Governance
Data Migration
QuickBooks → AWS/Aurora cutover workspace. The controlled staging seed completed through August 31, 2026; browser-driven import is still not deployed.
Controlled seed completed
Server-side QuickBooks staging seed, executed and verified in AWS.
The approved QuickBooks staging seed completed successfully through August 31, 2026. Posted history from that seed is what the actuals reporting endpoint now returns.
- Cutoff
- August 31, 2026
- GitHub Actions run
- 34274648727
- Batch ID
- fd6720e3-303e-53a9-83fb-44daaad34128
- Counts & totals
- See Migration verification below (server truth)
- Bank reconciliation
- See Bank statements at cutover below (server truth)
Bank tie-out is evidence-driven. The gate below stays open until bank-issued statement evidence is on file for every account and the server reports zero variance.
Migration verification
Record-by-record proof from AWS: counts and totals at the source against counts and totals loaded. Green only at exactly zero variance.
Loading from AWS staging…
Bank cutover tie-out
Statement ending balances against book balances at cutover, as reported by AWS.
The verification service has not reported bank cutover status yet.
Bank statements at cutover
Bank-issued statement evidence for the cutover tie-out. Nothing here posts to the General Ledger.
Statements on file
Choose a bank account to see the statements already stored for it.
Historical document detail still outstanding
Financial control totals tie exactly, but historical document detail did not come across one-for-one. This migration is not completely mapped.
These gaps do not change any balance — the trial balance, open A/P and open A/R tie to the cent — but the underlying source documents behind the history are incomplete, so drill-down into pre-cutover detail will not always find a record.
Chart of accounts
267 accounts exported from QuickBooks; 61 accounts in use were loaded.
Bills
20 historical bills in the export; 3 open bills were loaded.
Payments
21 historical payments in the export; 0 payment-subledger records were loaded.
Browser import status
Honest state of the self-service import pipeline.
There is no public QuickBooks import endpoint deployed for browser uploads. This workspace prepares and validates export artifacts, but it cannot load anything into AWS/Aurora itself — the completed seed above was run server-side under change control, not from this screen.
No import jobs are shown because none exist here; the job list will populate from the backend once an import 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.
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 — PENDING, no statements supplied
- Prior periods locked after acceptance; adjustments post as new journals