Governance
Data Migration
QuickBooks → AWS/Aurora cutover workspace. Preparation can start now; the authoritative import runs server-side once the AWS import endpoint is deployed.
Current status
Honest state of the cutover pipeline.
There is no authoritative QuickBooks import endpoint deployed on the AWS staging API yet. This workspace prepares and validates export artifacts, but it cannot load anything into AWS/Aurora, and it will never claim a file was loaded until the server confirms it.
No import jobs are shown because none exist — the job list will populate from the backend once the endpoint ships.
Prepare your QuickBooks exports
Gather these artifacts now so the cutover can run as soon as the endpoint is live.
Chart of Accounts export
QuickBooks: Reports → Account Listing. Include account numbers, types, and active state.
Trial Balance by period
One per period being migrated, run on the accrual basis, as of each period end.
Open A/R detail
Open invoices with customer, dates, terms, and open balance as of cutover.
Open A/P detail
Unpaid bills with vendor/station, dates, terms, and open balance as of cutover.
Customer & vendor lists
Legal/billing names, contacts, terms — feeds the organization registry.
Bank statements at cutover
Statement balances for every account, for the bank tie-out acceptance gate.
Spreadsheet format is used here because mapping is a working exercise — actuals reporting remains PDF-only.
Acceptance gates at cutover
The migration is accepted only when every gate passes server-side, with evidence.
- Imported Trial Balance equals QuickBooks Trial Balance per period, to the cent
- Open A/R detail ties to the A/R control account balance
- Open A/P detail ties to the A/P control account balance
- Bank GL balances tie to statement balances at cutover
- Prior periods locked after acceptance; adjustments post as new journals