What Actually Happens to Your QuickBooks History When You Migrate
Your historical transactions might not be coming with you. Decide what your history needs to do before the project begins, not after go-live.

You are moving from QuickBooks to Microsoft Dynamics 365 Business Central and want to know what to expect. The good news is that your new system will handle accounting, purchasing, inventory and reporting. But there is one detail that may not have been explained clearly.
Your historical transactions might not be coming with you.
You may be planning to migrate opening balances, outstanding invoices and customer records, leaving years of completed transactions behind in QuickBooks. That is a legitimate migration approach. It is also a decision with consequences for reporting, audits and daily operations.
That is why you need a strategy for your QuickBooks history before a QuickBooks to Business Central migration begins, not after go-live.
The decision that gets made without you
Most migration discussions focus on what the new system needs to operate: customers, vendors, items, general ledger accounts, opening balances, and outstanding receivables and payables.
Those are essential. But they are not the same as transaction history.
Suppose you have seven years of QuickBooks data. Your finance team regularly compares customer purchasing patterns, reviews historical margins and investigates transactions from previous financial periods. If only opening balances are migrated, Business Central starts with the financial position at cutover. It does not automatically contain the transactions that created that position.
Your historical financial statements may still be available in QuickBooks, but the detailed information is not necessarily accessible in Business Central. The migration can be technically successful while leaving your reporting team with less information than it had before. That is why historical data should be treated as a separate project decision.
Three ways history comes across
There are three common approaches to migrating QuickBooks information into Business Central.
1. Opening balances and open transactions
This is often the simplest approach. You migrate master data, opening general ledger balances, outstanding customer invoices, unpaid vendor bills and other information needed to begin operating. Historical completed transactions remain outside Business Central, and your new ERP starts from an agreed cutover date.
This can reduce migration complexity, particularly when historical data is inconsistent or poorly maintained.
2. Opening balances plus summarized history
The second approach brings over opening balances and selected historical financial information. For example, you might migrate monthly general ledger totals for previous financial years.
That allows finance to compare historical financial performance inside Business Central at a summarized level. You may see historical revenue by account and period without being able to drill into the original sales transactions.
3. Detailed historical transaction migration
The third approach is to migrate selected historical transactions at a more detailed level. This might include posted sales invoices, purchase invoices, payments, credit memos, general ledger activity and other records.
It requires more design, extraction, transformation and validation. The level of history available also depends on your QuickBooks product, source data, extraction methods and migration approach.
“We'll just keep QuickBooks for lookups”
This is one of the most common answers to the history question, and it can be perfectly reasonable: keep QuickBooks accessible for historical inquiries while Business Central becomes the operational system.
The difficulty is that “keep QuickBooks” needs a defined plan. You need to know who can access the historical company, how long access will remain available, whether the data can be exported and what happens when the old application is no longer supported or accessible. For example:
- A user investigating a customer balance may need to switch between Business Central and QuickBooks.
- A controller preparing a five-year comparison may need to combine two different data structures.
- An auditor may request supporting documentation from before the migration.
None of those situations is impossible to manage. But they should be anticipated.
A better approach may be to create a controlled historical archive, including exported transactions, financial statements and supporting documents, with a documented retrieval process. For some organizations, a separate reporting database or Power BI model can combine historical QuickBooks information with new Business Central data. That can preserve analytical continuity without forcing every old transaction into the new ERP.
Note: Keeping QuickBooks for lookups is a retention strategy only when access, ownership and retrieval have been planned.
How full transaction rebuilding works, at a high level
Detailed history migration is more complicated than exporting a spreadsheet and importing it into Business Central.
QuickBooks and Business Central have different data structures, posting processes and relationships between documents. A successful historical migration starts with deciding what needs to be preserved. That may include document numbers, transaction dates, customers, vendors, accounts, amounts, currencies, tax information, payment relationships and relevant dimensions.
Then the source data must be extracted and mapped to Business Central. For example:
- QuickBooks account structures may need to be mapped to Business Central general ledger accounts and dimensions.
- Historical customers and vendors need consistent identifiers.
- Transactions must be checked for missing references, duplicates, unsupported values and differences in accounting treatment.
The next decision is how to represent the history. There is an important distinction between importing historical journal entries and recreating historical posted documents. A general ledger journal may preserve financial amounts and dates, but it does not automatically reproduce the original invoice, payment application or document relationships.
The migration team must also consider closed periods, inventory costing, tax treatment and the risk of affecting current balances. Historical transactions should not be introduced in a way that distorts the opening financial position.
A detailed migration is not complete because the records imported successfully. It is complete when the migrated information reconciles and supports its intended use.
What cannot come across, regardless of approach
Not everything in QuickBooks can be recreated as an equivalent native Business Central record, mainly because the systems are different.
QuickBooks-specific workflow history, application settings, integration metadata and certain audit events may not have direct equivalents in Business Central. Attachments and supporting documents may require separate extraction and storage processes. Some historical relationships may be difficult to reproduce, particularly where source records have been modified, deleted or inconsistently maintained.
The original QuickBooks audit history also cannot simply become Business Central's native audit history. Business Central can record activity occurring within Business Central. Importing an old transaction does not recreate the original sequence of events that occurred in QuickBooks.
The question to ask every partner you shortlist
Ask this before accepting a migration proposal:
“Exactly which historical transactions will be available inside Business Central after go-live, and which will remain outside it?”
Do not accept “we migrate your data” as a complete answer. Ask the partner to show you the proposed migration scope. It should identify which records will be migrated as opening balances, which will be summarized, which will retain transaction-level detail and which will be archived.
Then ask how historical reporting will work:
- If finance needs five years of revenue comparisons, ask the partner to demonstrate how those comparisons will be produced.
- If auditors need old invoices, ask them to demonstrate how they will be retrieved.
- If historical customer transactions are included, clarify whether they will exist as native posted documents, imported financial entries or records in a separate reporting archive.
Those are materially different outcomes.
What you should consider
Before moving from QuickBooks to Business Central, decide what your historical information needs to do.
Separate operational requirements from reporting requirements. Determine which records employees must access inside Business Central, which can remain in a historical archive and which need to be available through Power BI or another reporting platform. Then choose the migration approach that supports those requirements.
Qixas Group helps organizations migrate from QuickBooks to Microsoft Dynamics 365 Business Central. We also recover ERP projects where important decisions about data, reporting and implementation scope were made too late.
Our approach starts with understanding what the business needs to preserve, not simply what can be imported.
Our recommendation is straightforward: define your historical reporting and audit requirements before approving a migration scope.
About the Author

Floyd Chan
President & Founder, Qixas Group
Floyd founded Qixas in 2007 after years of watching ERP projects fail for the same preventable reasons — junior staffing, slipping timelines, ballooning budgets. A Microsoft MVP and winner of the 2018 Directions Excellence Award, he is known across the Dynamics community as “the NAV genius.” He has been involved in more than 400 implementations and still reviews the hard ones personally.
- Microsoft MVP
- Dynamics NAV & Business Central
- ERP Upgrades
- Project Rescue
Frequently asked questions
Does my QuickBooks transaction history move to Business Central?
Only if the migration scope includes it. Many migrations bring across master data, opening balances and open receivables and payables, which lets Business Central start from the financial position at cutover without the transactions that created it. Summarized history and detailed transaction history are separate decisions with their own cost and effort.
What are the options for migrating QuickBooks history?
There are three common approaches: migrate opening balances and open transactions only; migrate opening balances plus summarized history, such as monthly general ledger totals for prior years; or migrate selected historical transactions at a detailed level, such as posted invoices, payments and credit memos.
Can we just keep QuickBooks for historical lookups?
Yes, if it is planned. Decide who can access the historical company, how long access will remain available, whether the data can be exported and what happens when the old application is no longer supported. A controlled archive or a reporting model that combines QuickBooks and Business Central data is often more dependable.
What QuickBooks data cannot be migrated to Business Central?
QuickBooks-specific workflow history, application settings, integration metadata and certain audit events have no direct Business Central equivalents. Attachments may need separate extraction and storage. The original QuickBooks audit trail also cannot become Business Central's native audit history, because importing a transaction does not recreate the events that produced it.
What should I ask a partner about QuickBooks data migration?
Ask exactly which historical transactions will be available inside Business Central after go-live and which will remain outside it. The proposed scope should show which records come across as opening balances, which are summarized, which keep transaction-level detail and which are archived, and whether migrated history exists as posted documents, journal entries or a separate reporting archive.
Read next

Seven Signs You've Outgrown QuickBooks (And Three Reasons to Stay)
Seven signs you have outgrown QuickBooks and need an ERP such as Business Central, from spreadsheet inventory to manual consolidation, and three situations where staying on QuickBooks is the right call.
Read more
Why We Don't Recommend Business Central to Every QuickBooks User
Do you need an ERP or is QuickBooks enough? Three business profiles that should stay on QuickBooks for now, the five operational thresholds that change the answer, and how to tell whether an ERP partner is qualifying you or selling you.
Read more
Dynamics GP to Business Central Migration Guide: Timeline, What Moves and Support Dates
How long a Dynamics GP to Business Central migration takes by complexity, what moves and what does not, and when Dynamics GP support ends.
Read moreKnow what your history will look like after go-live
We will map which QuickBooks records your team needs inside Business Central, which belong in an archive and how historical reporting will work before you approve a scope.
Book a Discovery Session