AccountEdge to QuickBooks Migration: Convert AccountEdge to QuickBooks Online

Yes, but not with a one click tool from Intuit. There is no AccountEdge option in the QuickBooks conversion tool and no Dataswitcher path for it, so a real AccountEdge to QuickBooks migration is assembled from three moves: export your lists, export your transaction history, and decide how much of that history is worth carrying. Firms that treat it that way finish in days. Firms that wait for an official button wait forever.

The good news is that AccountEdge does not lock your data up. Everything you need leaves the program as delimited text through one menu, and delimited text is exactly what a converter needs.

No. Intuit's supported conversions are narrow and worth knowing precisely, because most of the confusion in this decision comes from assuming they are broader than they are. Into QuickBooks Online, Intuit funds Dataswitcher for Sage 50 US edition and for Xero, and that route brings up to two fiscal years free with additional years available for a fee. Into QuickBooks Desktop, the conversion tool handles Sage 50 and Quicken.

AccountEdge appears on none of these. Neither does NetSuite, Sage Intacct, Sage 100 or Sage 300. When Intuit has no path, its published advice is the same every time: save what you need as Excel or CSV and import it. That is not a workaround, it is the documented answer.

It is also worth knowing what the supported paths leave behind, because it sets a realistic expectation for yours. Even on the routes Intuit funds, budgets, memorized transactions, invoice templates, sales orders, payroll records, projects, attachments and non posting entries do not convert. Nobody moves an accounting file whole.

This is the single most misread thing about AccountEdge right now, and getting it wrong changes your whole timeline. There are two different products called AccountEdge, sold by two different companies, in two different countries. Only one of them is closing.

MYOB AccountEdge, AccountEdge Network Edition and FirstEdge, the Australian products, were decommissioned on 28 February 2026. MYOB's notice states that company files in these products become read only after the next confirmation, so you can view historical data but cannot make changes. That is a hard stop, and Australian users had no choice about migrating.

The United States AccountEdge is a separate product and it is still being sold. As of September 2026 its own site publishes AccountEdge Pro at $20 per month for a single user, AccountEdge Network Edition at $30 per month including two users, and AccountEdge Hosted at $50 per month per user for browser access, with AccountEdge Connect from $15 per month. The site carries no sunset notice and states the company remains committed to desktop software.

So if you are a US business and you found an alarming shutdown notice, check the domain it came from. An Australian decommission page is not your deadline. You may still have excellent reasons to move to QuickBooks, but you are choosing to move, not being forced out this month, and that means you can do the migration on a clean fiscal boundary instead of in a panic.

Everything runs from one menu. Click File on the top menu bar, then Export Data, then the category and subcategory you want, for example Accounts then Account Information, or Cards then Customer Cards. AccountEdge writes either a tab delimited or a comma separated text file, and comma separated is the safer default because it is also one of only two formats AccountEdge itself will read back in.

Two habits save rework. Take a backup of the company file before you start exporting, and do the export work when nobody else is in the file, because multi user access interferes with data export. Neither costs you anything if you plan for them and both cost an afternoon if you do not.

One quirk catches people out: AccountEdge is a text file program, not a spreadsheet program. If you open an export in Excel and save it back, you can silently change dates and strip leading zeros from account numbers and check numbers. Convert straight from the exported file where you can.

Use Transaction Journal Entries. It is the export that maps to a bank register, and it lets you choose the journal and restrict the entries to a time period, which is how you pull a single month or a single fiscal year rather than everything at once.

Two journals carry the money movement. Disbursements filters to Spend Money, Pay Employees, Pay Bills, Customer Refunds, or All. Receipts filters to Receive Money, Customer Payments, Vendor Refunds, or All. For a bank account you generally want All on both sides, exported for the same date range, so the debits and the credits arrive together and the period reconciles.

The other exports answer other questions. Accounts exports balances from the current or previous fiscal year once you select the period whose ending balances you want, which is what you need for opening balances at cutover. Cards can be filtered by identifier and postal code. Sales and Purchases can be restricted by customer and vendor identifier, by time period, by layout, and by status so you can pull only what is still open. Inventory Adjustments takes a time period.

Export by fiscal year rather than in one giant pull. Smaller files reconcile faster, and if one year is wrong you re-do one year.

QuickBooks Online will take a plain CSV upload, and for a small file that is the fastest path. The format it wants is three columns of Date, Description and Amount, or four columns of Date, Description, Credit and Debit. Uploads are limited to 1,000 transactions and 350 KB, and the file must be in English. Accepted extensions are .csv, .txt, .qbo and .ofx.

Those caps are where an AccountEdge export usually breaks. A year of Receipts and Disbursements from an active company is comfortably past 1,000 rows, so a straight CSV upload turns into splitting the file by hand and hoping the split does not land mid month. Converting the export to a .qbo file removes the row problem and adds something a CSV cannot carry.

That something is the FITID. Every transaction in a .qbo file has a unique identifier, QuickBooks skips identifiers it has already seen, and it remembers them even after you delete the transaction. A CSV has no transaction identifier at all, which is why re-uploading an overlapping CSV range duplicates everything while re-importing an overlapping .qbo range quietly does nothing. During a migration, where you will almost certainly re-run at least one period, that difference is the whole ball game.

Watch the date format. Intuit's most widely surfaced CSV formatting article is the global edition and recommends DD/MM/YYYY, which is wrong for a US company file and mis-posts every transaction dated the 1st through the 12th without ever showing an error. Use the sign convention too: one Amount column, positive for money in and negative for money out, with a minus sign rather than parentheses, and remember credit card accounts flip that meaning.

Not directly, and the constraint here is firmer than most people expect. QuickBooks Desktop cannot import a bank CSV in any version. The Import Excel and CSV Toolkit handles exactly four list types, customers, vendors, items and chart of accounts, and nothing else. For transactions your only routes are a .qbo file through Bank Feeds or an IIF file.

Prefer .qbo. It arrives in the Bank Feeds review queue where you accept or correct each row and QuickBooks matches duplicates for you. IIF posts straight to the ledger with no undo, which is a bad property during a conversion when the first attempt is rarely the final one. QuickBooks Online cannot import IIF at all.

If you are landing in Desktop and expect to move to QuickBooks Online later, there is a clock worth knowing now. Intuit limits importing a QuickBooks Desktop company file into QuickBooks Online to 90 days from when the Online company was created, or 180 days if an accountant created it through QuickBooks Online Accountant. That window does not apply to file by file .qbo imports through Bank Feeds, which is a quiet advantage of the converter route: it never expires.

A large share of AccountEdge users are on Mac, and this is where the move gets decided. AccountEdge built its US following as the serious Mac desktop accounting package, so the natural instinct is to look for the Mac version of QuickBooks Desktop and land there. That instinct is now a dead end.

Intuit stopped new sales of QuickBooks Desktop Pro, Premier and Mac Plus in September 2024. The 2024 release is the final non Enterprise version, supported through 30 September 2027, and Enterprise, which is still sold and supported, is Windows only. There is no Mac desktop QuickBooks to migrate into for the long run.

In practice that means a Mac AccountEdge user is choosing QuickBooks Online, and should plan the conversion for QuickBooks Online from the first export rather than routing through a Desktop file that has a support end date and an import clock attached to it. If you want the mechanics for the ongoing workflow after cutover, the CSV to QBO converter for Mac covers running conversions without a Windows machine anywhere in the process.

Worth answering honestly, because migration is expensive and a bad reason to move is still a bad reason.

AccountEdge wins on cost and on ownership. At $20 per month for AccountEdge Pro it is materially cheaper than a comparable QuickBooks Online subscription, it runs on your machine, and it does not change under you when a vendor ships an update. For a stable single entity business with a bookkeeper who knows the program, there is no accounting reason to move.

QuickBooks wins on everything that touches other people. Your accountant almost certainly works in QuickBooks. Your bank almost certainly has a QuickBooks feed. Payroll, receipt capture, point of sale and lending integrations are built for QuickBooks first. The strongest arguments for migrating are ecosystem arguments, not feature arguments, and they get stronger every year rather than weaker.

The realistic trigger is usually one of three things: the accountant charges more to work in AccountEdge than the software costs, the business needs remote or multi user access that desktop makes awkward, or an integration the business now depends on simply does not exist for AccountEdge. If none of those apply, staying is a legitimate answer.

It depends entirely on whether you convert history or just open balances, and the spread is wide.

Doing it yourself costs software time. AccountEdge exports are free, and the cost is converting the exports and reconciling the result. Conversion services price by complexity rather than by source system: Numerawise, which lists AccountEdge among its supported platforms, publishes general bands of from $500 for a small single entity, $2,000 to $5,000 for mid market files with inventory or payroll, and $5,000 to $15,000 for multi entity or large ERP work, with a fixed price quote after a scoping call. Those are the vendor's published bands, not a quote for your file.

On the tooling side, Rightworks Transaction Pro publishes QuickBooks Online plans at $13, $39 and $61 per month, or $120, $350 and $570 annually, where the entry plan caps at 200 rows of data per month, plus QuickBooks Desktop licenses at $199 and $299 one time per user with one year of email support and a $99 annual fee after that. Our own conversions run 3 free with no account, then $49 per month for 100 conversions or $24 per month billed yearly, with unique transaction IDs and conversion history on the $149 tier.

The largest lever is not the tool, it is the scope. Converting three years of transaction detail costs several times what converting opening balances plus the current fiscal year costs, and for most businesses the older detail is queried roughly never. Keeping AccountEdge installed and readable for lookups is usually cheaper than paying to convert data into QuickBooks so it can sit there unread.

Plan on one to three weeks for a straightforward single entity file, most of it spent reconciling rather than converting. The exports take an afternoon. Matching the converted balances back to AccountEdge is the work.

The sequence that goes wrong least: pick a cutover date on a closed period boundary, run a final reconciliation in AccountEdge, export and load the lists first, enter opening balances as of the cutover, then bring transaction history in one fiscal year at a time from newest to oldest, reconciling each year before starting the next. Loading history before lists is the most common self inflicted delay, because transactions land against accounts and names that do not exist yet.

Do not decommission AccountEdge on cutover day. Keep it installed and readable through at least one full close and one tax filing in QuickBooks. The cost of keeping it around is nothing next to the cost of discovering in March that a detail you need is only in the old system.

Three failures account for most of the cleanup, and all three are easier to catch than to fix later.

Opening Balance Equity that will not clear. It is a temporary placeholder and should be zero once setup is done. If it is not, something loaded without a matching entry. Where the balance ultimately belongs depends on entity type: sole proprietor to Owner's Equity, partnership to Partner's Capital, S or C corporation to Retained Earnings.

Dates that shifted. Two digit years resolve as 00 to 29 meaning 2000 to 2029 and 30 to 99 meaning 1930 to 1999, and Windows Excel defaults to the 1900 date system while Mac historically used 1904, a four year and one day difference. On a Mac to Windows migration, which is exactly what an AccountEdge move often is, that is a live risk rather than a theoretical one.

A period that will not reconcile. Three quick diagnostics narrow it fast. A difference that divides evenly by nine is transposed digits. A difference equal to exactly twice a transaction is a sign flip. A difference matching one transaction exactly is a row that did not convert, or one that was accepted twice.

Export the journal you need from AccountEdge with File then Export Data, drop the file into the converter at the top of this page, and get back a .qbo file QuickBooks Online or QuickBooks Desktop will accept. The first three conversions need no account and no card, which is enough to test a real month from your own file before deciding anything.