VAST Migration
Current progress
An ongoing QuickBooks Desktop to Zoho migration, supported by a custom Windows exporter, source-linked imports, and detailed accounting and inventory reconciliation.
The challenge
Move VAST’s accounting and inventory workflows into Zoho while preserving source identities, business relationships, and a verifiable path to reconciliation.
Work in progress
The work includes a read-only .NET exporter, migration mapping, customer and catalog imports, CRM relationship handling, recovery tooling, and reconciliation workflows. The overall migration remains in progress.
- Read-only Windows/.NET QuickBooks exporter
- Source provenance and identity-preserving mappings
- Customer, vendor, catalog, and warehouse migration work
- CRM relationship handling and protected existing records
- Accounting and inventory reconciliation
- Bounded imports, readback verification, and recovery receipts
Crew on this contract
The VAST QuickBooks migration to Zoho is ongoing. This case describes implemented extraction and import tooling while keeping cutover, financial reconciliation and final acceptance separate.
A business migration still in progress
VAST is an ongoing QuickBooks Desktop to Zoho migration covering accounting and inventory foundations, customer and vendor records, catalog data, and the relationships needed to carry business history forward. The work is not complete, and production cutover and full reconciliation are not being claimed.
A custom Windows exporter
I built a read-only Windows exporter using .NET and the QuickBooks SDK. It works against a separately restored company-file copy and binds the export session to that selected file. The resulting migration package carries source provenance so later transformations can be traced back to the input.
The exporter is one part of the migration. Source extraction, target mapping, import preparation, and acceptance each have their own responsibilities; a successful export does not by itself establish that the target system is ready to operate.
Preserving meaning across systems
The migration work includes customer identity matching, active/inactive status, vendor relationships, product fields, warehouse/bin information, and links to existing CRM records. Ambiguous identities and unresolved terms are treated as explicit cases for review rather than silently merged or guessed.
Financial and inventory reconciliation requires more than matching list counts. Opening quantities, valuation, accounts, and transaction-history relationships must be evaluated together. The current work separates those questions from nonfinancial master-data progress.
Controlled execution and recovery
Imports are prepared in bounded groups with source references, readback verification, and retained receipts. Recovery work distinguishes a confirmed write from an uncertain attempt so that retries do not become uncontrolled duplicate operations.
The project demonstrates the engineering behind an operational migration: custom extraction, data modeling, reconciliation, API work, and a reviewable path toward acceptance. Shipping and later integrations remain part of the phased plan rather than evidence of a completed launch.
Related work: Fortune’s operational data bridge and data migration and systems integration.
What this project clarifies
A migration review needs more than an export count. Identify the records that must retain their relationships and the balances or quantities that need independent reconciliation before the destination becomes operational.
For a related project, see business systems integration.
Have something like this in mind?
This is the kind of build I take on. Book a call and we'll scope yours.