jaz-conversionlisted

Use this skill when migrating accounting data into Jaz — importing from Xero, QuickBooks, Sage, MYOB, or Excel exports. Covers the full conversion pipeline: analyzing source files, mapping Chart of Accounts, contacts, tax profiles, and items, creating clearing accounts, running TTB (trial transaction balance), and verifying TB. Also use when the user mentions data migration, conversion, import, or switching accounting software — whenever a customer's prior system is Xero, QuickBooks, Sage, MYOB, or an Excel-based ledger.
teamtinvio/jaz-ai · ★ 4 · Data & Documents · score 80

Install: claude install-skill teamtinvio/jaz-ai

# Jaz Conversion Skill You are performing an **accounting data conversion** — migrating a customer's financial data from their previous accounting software (Xero, QuickBooks, Sage, MYOB, or Excel-based systems) into Jaz. > **Jaz-native, not generic.** The clearing-account pattern, the CoA-bulk-upsert all-or-nothing semantics, the `currencyCode`-string-silently-ignored-on-invoices gotcha, the `bulk_upsert_invoices` PARTIAL_SUCCESS path — every rule in this skill is an opinion shaped by Jaz's specific API behavior, not by generic migration theory. Source-system mapping (Xero, QB, Sage) is included only as input parsing; everything downstream is Jaz-shaped. **This skill provides Jaz-contextual conversion domain knowledge. For API details (field names, endpoints, gotchas), load the `jaz-api` skill alongside this one.** ## Guided in-app data transfer Jaz also has a guided **Data Transfer** flow available in Settings (Xero, QuickBooks, Sage, MYOB). ## When to Use This Skill - Analyzing customer-provided Excel/CSV files for conversion - Mapping source Chart of Accounts, contacts, tax codes, or items to Jaz - Creating conversion transactions (invoices, bills, journals) - Building or reviewing TTB (Transfer Trial Balance) entries - Verifying post-conversion Trial Balance accuracy - Troubleshooting TB mismatches after a conversion ## Three Conversion Types All types use the **same pipeline** — only the scope (which entity types) differs. ### Config Mode (foundation only) - **