No — this is build-to-order, not an instant AppSource install. After purchase we scope your source system and data volume, then build and install the per-tenant extension on your sandbox. Typical delivery is about one working week depending on how many source systems, how much history you want migrated, and how clean the data is. We confirm a firm timeline during scoping before any build work begins.

Because the extension stays installed on your tenant, we support re-runs and post-cutover fixes. The build includes a support window for reconciliation issues and follow-up batches found after go-live. We also keep the extension compatible with your Business Central version through its scheduled updates, and offer an optional ongoing support arrangement for future source-data top-ups or additional migrations.

QuickBooks Desktop (via IIF/list exports), QuickBooks Online, Xero and Sage 50. It migrates master data (customers, vendors, items, chart of accounts), open balances (posted as opening ledger entries), and historical transactions up to a cut-off date you choose. Exact scope is agreed during the mapping phase.

Every migration runs as a dry run first. The validation pass flags duplicates, unmapped accounts, missing dimensions and unbalanced entries, then produces a reconciliation report comparing legacy G/L, aged receivables and aged payables to the BC result. You sign off on that report before we post anything to production.

The tool is built around rollback safety. Staged batches can be reversed before posting, and opening journals are isolated so they can be cleanly reversed and re-posted. This means a failed or incomplete run can be corrected without leaving orphaned entries in your live ledgers.

The extension runs inside your own Business Central tenant — staging data lives in custom tables in your environment, not on an external service. Access is gated behind a dedicated permission set, every run is audit-logged, and OData/REST connections to QuickBooks Online or Xero use your own API credentials.