jaz-conversion

Migrate accounting data into Jaz with opening balances and audit trails.

5|3|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/teamtinvio/jaz-ai --skill jaz-conversion
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jaz-conversion
Source: https://github.com/teamtinvio/jaz-ai/tree/main/cli/assets/skills/conversion
Command: npx skills add https://github.com/teamtinvio/jaz-ai --skill jaz-conversion

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migration of complete and audit-ready accounting data into Jaz, preserving opening balances, trial balances, and the full transaction history to support seamless transitions.

Core Features & Use Cases

  • Supports Quick Conversion (opening balances at the fiscal year end) and Full Conversion (complete FY history) with CoA mapping, contact and item discovery, currency enablement, tax and FX handling, and opening-balance journals.
  • Handles AR/AP aging, currency rates, and TTB journaling to ensure balance alignment and zero unrealized FX gains where required.
  • Includes idempotent cleanup of stale conversion artifacts and robust rollback safety to protect data integrity during re-runs.

Quick Start

Load your source CoA, TB, AR/AP aging, and contacts, then start the Jaz conversion workflow to establish currencies, map accounts, and apply the opening balances.

Frequently Asked Questions about jaz-conversion

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate accounting data into Jaz while preserving opening balances?

Accounting data migration into Jaz preserves opening balances and audit trails by orchestrating CoA bulk-upsert, currency setup, and opening-balance journal entries with appropriate lock dates. It supports both Quick Conversion at fiscal year end and Full Conversion of complete transaction history.

What is the difference between Quick Conversion and Full Conversion for accounting data migration?

Quick Conversion migrates only opening balances at the fiscal year end (FYE), while Full Conversion migrates the complete financial year transaction history. Both approaches handle CoA mapping, contacts, currency enablement, and FX handling to ensure accurate trial balance alignment.

How do I map my source Chart of Accounts during the Jaz data migration?

Jaz data migration maps your source Chart of Accounts through a bulk-upsert process that aligns accounts with opening balances and trial balances. You load your source CoA and trial balance data, then the workflow establishes currencies and applies the account mappings.

Can I migrate AR/AP aging and foreign exchange data into Jaz?

Yes, Jaz migration handles AR/AP aging, currency rates, and FX handling to ensure trial balance alignment and zero unrealized FX gains. The workflow establishes currencies, applies tax and FX treatment, and generates opening-balance journals with appropriate lock dates.

What source data do I need to prepare before starting a Jaz accounting conversion?

You need to load your source Chart of Accounts, Trial Balance, AR/AP aging, and contacts before starting the Jaz conversion workflow. These inputs allow the process to establish currencies, map accounts, and apply opening balances accurately.

Is it safe to re-run an accounting data migration if the initial conversion fails?

Re-running the Jaz accounting migration is safe due to idempotent cleanup of stale conversion artifacts and robust rollback safety. These mechanisms protect data integrity and allow you to retry the conversion workflow without duplicating journal entries or corrupting balances.