Converting from MYOB or AccountEdge to QuickBooks
How QuickBooks users move data from MYOB and AccountEdge, the export-and-map process, regional tax issues, and transaction-history limitations.
QuickBooks users switching from MYOB and AccountEdge regularly run into the same question: how do you actually move the data over, and what regional complications should you plan for? The short answer is that there is no single official tool that lifts an MYOB or AccountEdge file directly into QuickBooks. The move is an export-and-map process, and the details matter.
Understanding the product lineage
MYOB and AccountEdge are closely related products from the same software lineage. AccountEdge is the desktop product long used on Mac and in the US market, while MYOB is widely used across Australia and New Zealand. That shared origin means the export steps are similar regardless of which one you are leaving, but the destination configuration in QuickBooks can differ depending on where your business operates.
What exports and what does not
From MYOB or AccountEdge, you export the building blocks of your books: the chart of accounts, customer records, vendor records, and item lists. These typically export to CSV or text files. Alongside those lists, you pull the trial balance and your aged receivables and payables as of your chosen cutover date.
Those exported lists populate the equivalent lists in QuickBooks, and the balances go in as opening balances. The approach is clean and workable, but it comes with a structural limitation. Full transaction history does not survive a plain CSV-based export. The format carries your current lists and balances, but not the individual transactions — invoices, bills, payments, journal entries — that produced those balances over time.
Because of that, many businesses convert on a clean cutover model. They bring their lists and opening balances into QuickBooks as of a specific date, then record all new activity going forward in QuickBooks. Prior periods remain referenced through those opening balances rather than reproduced transaction by transaction.
The two regional gotchas
Two complications catch users off guard, and both are worth planning for before you start exporting.
Tax configuration
An Australian or New Zealand MYOB file is built around GST rules specific to those jurisdictions. That tax structure cannot simply be copied across into QuickBooks. It has to be reconfigured for the correct regional edition of QuickBooks you are moving to. Getting this wrong means your tax reporting will be off from day one, and correcting it after the fact is harder than setting it up correctly during the conversion.
Platform differences
AccountEdge has historically been a Mac product. If your organization has been running it on Mac hardware, you need to plan for the Mac-to-QuickBooks side of the transition in addition to the data mapping itself. QuickBooks Desktop for Mac and QuickBooks Desktop for Windows have different capabilities, and the choice affects how you structure the migration.
When a plain CSV export is not enough
The CSV route works for lists and balances. It falls short when a business needs genuine transaction history in QuickBooks — actual invoices, bills, and payments that reconcile back to the original MYOB or AccountEdge file. It also gets complicated when a conversion crosses both regions and platforms at the same time, such as moving an Australian MYOB file on Mac into a US edition of QuickBooks on Windows.
In those situations, users have reported that a professional conversion service is the practical route. A dedicated conversion can map the exported data more thoroughly, bring over transaction detail beyond what a plain CSV carries, set up the correct regional tax configuration, and verify the finished QuickBooks file against the original balances in MYOB or AccountEdge.
Planning the cutover
The businesses that report the smoothest conversions tend to pick a clean cutover date and work backward from it. They export their lists and balances as of that date, accept that prior-period detail will live in the old system or in reports rather than in QuickBooks, and focus on getting the opening balances and tax setup right from the start.
For users who need more than that — full reconcilable history, cross-region moves, or platform changes alongside the data migration — the export-and-map process alone is usually not sufficient. The limitation is not in the export step itself but in what CSV files can carry. Understanding that boundary before you begin is the difference between a controlled conversion and a frustrating one.