AccountEdge/MYOB → QuickBooks

Source formats accepted and why

We accept three source formats: a .zip export from AccountEdge, a .myo file from older MYOB releases (typically pre-2020), and a .myox file from current MYOB releases. Each format is parsed against the same internal canonical representation and the resulting QuickBooks Desktop file is structurally identical regardless of which source format you started from. That equivalence matters when a practice has files from multiple eras — the resulting QuickBooks files line up cleanly against each other and reporting at the practice level becomes consistent without a separate normalization pass after the migration is done.

What the audit document records

The audit document maps every non-trivial transformation between the source platform and the QuickBooks destination, organized by file area: chart of accounts mapping, customer and vendor list reconciliation, item structure conversion, payroll year-to-date carryforward, sales-tax code translation, class and location handling, custom-field disposition, and any AccountEdge or MYOB feature with no QuickBooks counterpart. The document is structured so a reviewing accountant can read it linearly and walk away with a complete picture of every decision the migration made. Reviewers we have worked with consistently treat the document as sufficient evidence.

Why one to two business days, not same day

Platform migrations are categorically more involved than even the Complex Enterprise conversion in this Portal because the source and destination data models are not just different versions of the same product — they are different products with different conventions for accounts, items, payroll, and sales tax. The diagnostic phase is longer, the canonical-representation pass is real engineering work, and the verification step has to confirm correctness across two structurally different schemas. One to two business days is an honest target; we do not compress it artificially to look better next to single-day services that target a much narrower scope.

Will my historical reports still match after the migration?

Period-level historical reports — monthly P&Ls, quarterly trial balances, annual balance sheets — match the source platform's reports dollar-for-dollar at every period close as a hard verification gate. Detail-level reports against AccountEdge or MYOB-native reporting features may not have a direct QuickBooks counterpart and need to be rebuilt in QuickBooks's report writer. The audit document calls those out individually so you know which reports need a rebuild before the migration concludes. Most practices find the rebuild is straightforward once the underlying data has landed cleanly in the destination.

How is payroll history carried across?

Every active employee comes across with year-to-date payroll figures as of the migration cutoff date, mapped onto QuickBooks Desktop's payroll item structure for Canadian payroll. Historical payroll runs prior to the cutoff are summarized rather than reposted at full per-paycheque detail, which is the standard practice for cross-platform migrations and avoids re-running source-deductions calculations against a different platform's tax engine. The audit document records the cutoff date and the summarization approach so the deliverable is auditable on payroll specifically.

What if my AccountEdge or MYOB file uses features QuickBooks does not have?

Some AccountEdge and MYOB features have no first-party QuickBooks counterpart — particular custom report types, certain UI-level customizations, specific job-tracking shapes that overlap with QuickBooks's class and location model rather than living in their own dedicated structure. The audit document calls every one of those out, with a recommended QuickBooks-native pattern that captures the same operational intent. We do not silently invent half-mapped equivalents during processing; if a feature has no clean destination, the document names it as such and recommends the closest native pattern.

Can I migrate to QuickBooks Online instead of Desktop?

This service targets QuickBooks Desktop (Premier or Pro) as the destination. If your end goal is QuickBooks Online, the recommended path is to migrate to Desktop first using this service, then run the QBO Readiness Report on the resulting file, then execute Intuit's Desktop-to-QBO migration with any pre-migration remediation the readiness report recommends. The two-step approach yields cleaner data than going directly cross-platform to QBO because the canonicalization step is done in a structured environment rather than during Intuit's QBO import, which has different behaviour.