Migrate from QuickBooks Online

Evenbead imports a QuickBooks Online company through Intuit's Accounting API into the same export bundle, tie-out and importer as a Desktop migration: nothing is imported until the copy matches QuickBooks Online's trial balance to the cent at every month-end.

How it will work

Connect. A person with the admin scope starts a connection for an export date (POST /v1/migrations/qbo/connections, or the web app's Migration page) and signs in to Intuit to approve read-only access. QuickBooks Online has no service accounts, so a person with the company's QuickBooks login does this step.
Estimate. Intuit meters API reads for apps like ours. Evenbead counts your records first and shows how many calls the extraction will take (POST .../estimate).
Extract. Lists, transactions and reports are read page by page (POST .../extract), then the tie-out runs (GET .../tieout).
Read the disclosure. Some things QuickBooks Online does not export through its API (for example its audit log, full reconciliation state, bank rules and attachments). Evenbead lists what your company has that will not come over, and how each item is handled (GET .../disclosure).
Import into empty books (people only), then cut over, which revokes the connection at Intuit and wipes the stored tokens.

Tokens are encrypted at rest and refreshed as Intuit requires; revoking the connection (POST .../revoke) ends access at once.

Until then

Export your QuickBooks Online reports (trial balance, general ledger, AR/AP aging) as of your cutover date and keep them: they are what any migration ties out against.
If you still have a QuickBooks Desktop file for the same company, the Desktop migration works today.