How to migrate from MYOB to Xero

Migrating accounting software can feel like a high‑risk move, mainly because “data loss” sounds permanent. In practice, most MYOB to Xero migrations succeed when they’re treated like a controlled changeover: the MYOB file is cleaned and reconciled first, the conversion is done off a frozen snapshot, and the new Xero file is validated against MYOB reports before anyone relies on it.

Xero’s standard approach for many MYOB desktop files is a hands‑free conversion using Jet Convert, where the file is prepared, uploaded, and returned as a new Xero organisation with an action checklist to complete setup.

What “without losing data” really means

The important nuance is that “no data loss” does not always mean “every historical detail is imported into Xero forever.” Most successful projects preserve data in two ways: enough history is converted into Xero to keep day‑to‑day operations and reporting smooth, and the MYOB file is retained as an archive for deep historical lookup, audits, and edge cases.

This approach is common because importing excessive transaction history can slow a ledger and because some MYOB file types and features don’t convert cleanly, even with specialist tools.​

The three migration paths (and when each is used)

Most MYOB to Xero migrations land in one of these patterns.

1) Hands‑free conversion (Jet Convert)

If the business is on a supported MYOB desktop product, this is usually the cleanest and fastest path. Xero explicitly promotes Jet Convert as its conversion partner for moving clients off specified MYOB desktop products, and outlines the basic steps: prepare the file, upload it, then receive the Xero subscription and converted data along with an action checklist.​

Xero also repeats the same “upload → receive subscription and action checklist within a few business days” workflow on its small business conversion page.​

Jet Convert’s own guidance is consistent with this, noting that the conversion takes up to 3 business days for MYOB desktop files and up to 5 business days for other software types, and that you’ll receive a post‑conversion action checklist.​

2) Self‑service conversion tools (manual import)

If the MYOB product or file type isn’t supported for automated conversion, Xero points users toward a self‑service toolbox for conversion. This generally means exporting data from MYOB and importing it into Xero using templates and conversion settings, then manually checking balances and outstanding items.

This path is workable for simpler businesses, but it becomes more fragile when inventory, payroll complexity, and years of messy historical data are involved.

3) Hybrid migration (opening balances + MYOB archive)

Some files simply aren’t good candidates for a full history conversion. iKeep Bookkeeping lists examples they do not convert via Jet Convert workflows, including MYOB Essentials, multi‑currency or multi‑location files, files with negative inventory, very large files, and files using WET/WEG; in those scenarios they recommend waiting until financial year end and importing opening balances into Xero while keeping MYOB read‑only for history.​

This hybrid approach is often the safest way to avoid data integrity issues when the MYOB file is complex or has known conversion blockers.

Step 1: Confirm your MYOB file is eligible

Before planning dates or training staff, confirm the product version and the file features in use, because eligibility determines the path.

Xero’s “Help your clients move off desktop” page lists the MYOB products able to be converted by Jet Convert as MYOB AccountRight Live, Standard, Plus, and Premier. Jet Convert’s MYOB file preparation page also emphasises that preparation and correct package selection is required and that conversion times start only after key prerequisites are completed.

If you’re not on a supported desktop product, or if the file uses complex features that are known to create conversion issues, treat it as a likely hybrid migration and plan for opening balances plus keeping MYOB as archive history.​

Step 2: Prepare the MYOB file

Conversion tools don’t “fix” accounting files. They copy what’s there. That’s why the pre‑migration clean‑up is usually the highest leverage work you do.

Jet Convert explicitly states that “the cleaner your data, the smoother your conversion to Xero,” and its preparation page highlights creating a backup, selecting the conversion package, mapping bank accounts (where required), and completing steps before conversion timing begins.​

A detailed conversion checklist published by Jet Convert includes pre‑conversion checks such as ensuring clearing accounts (including undeposited funds and electronic clearing) are reconciled to nil, ensuring payables reconcile to supplier statements, ensuring credit notes are applied unless unused, and repeating similar checks for receivables.​

Practical MYOB preparation checklist (high impact)

• Reconcile bank and credit card accounts to the cut‑over date (and resolve unreconciled items).​

• Reconcile clearing accounts to zero (undeposited funds and electronic clearing accounts in particular).​

• Confirm receivables and payables are real (apply credit notes, write off old junk, ensure reports reconcile).​

• Back up the file before uploading or exporting (especially for desktop).​

• Fix known blockers early (negative inventory, unsupported file types, special tax codes) or plan a balances‑only approach.​

Step 3: Pick a cut‑over date and freeze the MYOB file

The migration is only as accurate as the snapshot you convert.

Jet Convert’s process and timelines assume the conversion is run off a stable file. Their timing starts only once package selection and access/mapping steps are completed, and they note different turnaround times for desktop vs online conversions.​

A practical rule used by many bookkeepers is to choose a logical break point (end of month or end of financial year), then stop processing new transactions in MYOB once the file is ready for conversion. The goal is one definitive “last day in MYOB” so the comparison reports line up cleanly.

Step 4: Run the conversion

If you’re doing the hands‑free pathway, Xero’s process is straightforward.

Prepare the desktop file, then upload the client’s file through Jet Convert, providing a Xero subscription email so Jet Convert can create the organisation.​

Within a few business days, Jet Convert creates and sets up the Xero subscription, converts the data, and sends the converted file plus an action checklist. Jet Convert’s own support article confirms that once complete you receive an email with the post‑conversion action checklist and that taking over the Xero subscription happens via an email link from xero.com.

Turnaround times are also stated clearly by Jet Convert: up to 3 business days for MYOB desktop files and up to 5 business days for other software types.​

Step 5: Validate the data in Xero

A migration is not “done” when you get access to the Xero organisation. It’s done when Xero’s numbers agree with MYOB’s numbers and you understand any intentional differences.

Jet Convert emphasises the action checklist and recommends following it closely. It also publishes support guidance suggesting reaching out within 7 business days of receiving the conversion so they can review data while it remains unchanged.

Validation checks to run

• Compare trial balance at the cut‑over date (MYOB vs Xero).

• Compare bank balances (Xero vs bank statements, and against the final MYOB reconciliations).​

• Compare aged receivables and payables, and confirm old credits and unapplied items are handled correctly.​

If something is off, resist the urge to “patch” it with ad‑hoc journals until you understand the cause, because quick fixes can create long tail reconciliation problems later.

Step 6: Rebuild your live workflows

Even in a great conversion, there’s always post‑conversion setup work. The objective is to make Xero your new operational truth going forward.

Typical post‑conversion tasks include setting up bank feeds, creating bank rules, confirming invoice templates, re‑connecting payment services, re‑creating repeating invoices/bills, and ensuring user permissions are correct. Jet Convert’s own guide includes post‑conversion optimisation tasks like reviewing the dashboard watchlist, deciding on processes to maximise bank feeds, and customising invoice setup and payment gateways.​

Payroll often needs special attention because it touches compliance and employee reporting. Regardless of which system you move from, expect payroll to require careful verification in the new platform.

Common pitfalls (and how to avoid them)

Most MYOB to Xero “data loss” stories are actually data integrity stories.

• Converting an unreconciled MYOB file and expecting the converter to “sort it out” (it won’t).​

• Moving mid‑month with unclear cut‑over rules, then trying to stitch two systems together after the fact.

• Assuming inventory and payroll will convert perfectly in complex files, especially where the file type itself is flagged as not suitable for conversion.​

• Not keeping an archive of the MYOB file for historical lookup, especially when choosing a balances‑only migration approach.​

A note on getting help (Hume Bookkeeping)

Many businesses can technically migrate themselves, especially if the file is small and clean. Where migrations usually get risky is when there’s inventory complexity, payroll complexity, years of legacy data, or no clear cut‑over and validation plan.

If you’d like a migration that’s designed as a controlled changeover (with pre‑conversion cleanup, cut‑over planning, post‑conversion checks, and an audit‑friendly outcome), that’s the kind of MYOB to Xero migration and Xero setup support Hume Bookkeeping can provide.