Merge a QuickBooks File That Was Started by Mistake
Someone started a new company file instead of continuing the old one. We merge the two back into a single continuous set of books, with invoices raised in one file and paid in the other still matched up.
Request a QuoteIt is one of the most common ways a business ends up with two QuickBooks files, and it almost never happens deliberately. The old file was slow, or threw an error, or someone was told a fresh start would fix a problem. A new company file was created, work continued in it, and by the time anyone realised the history had been left behind, there were months of transactions on the wrong side of the line.
Why This One Is Usually Straightforward
Of all the reasons to merge two company files, this is generally the most tractable — because the split is chronological. One file stops, the other starts. There is a clean date boundary, which is exactly the thing that makes most other merges complicated.
That matters because the date range is normally the sharpest decision in a merge. Here it usually makes itself: everything in the second file comes across, because everything in the second file belongs to the same continuous set of books.
The One Thing That Actually Goes Wrong
The complication in this scenario is rarely the dates. It is the relationships that straddle them.
When a file changes over mid-trading, invoices raised in the old file get paid in the new one. Bills entered before the switch get settled after it. Purchase orders raised on one side are fulfilled on the other. Those relationships are the difference between an aging report that means something and a list of open items nobody can explain.
Because both ends of those relationships exist — one in each file — a full merge reconnects them. This is why we usually recommend merging the second file in its entirety rather than from a convenient recent date: a partial range is what breaks the invoice-to-payment chain, not the merge itself.
Where a relationship genuinely cannot be reconnected, it is reported rather than guessed at. You get a list, by name, date and amount, of every transaction that arrived unapplied.
Watch for an Overlap
The version of this scenario that needs more care is when the two files overlap — when, for a period, transactions were being entered in both. That usually happens when part of the team kept working in the old file after the new one was created.
Merging an overlapping period without handling it double-counts every transaction in it. During the evaluation we identify any overlap and agree with you which file is authoritative for those dates, so only one copy is carried across. If you think this might apply to you, say so up front; it changes the scope.
What You Get Back
A single continuous company file, both originals untouched, and a report showing what matched, what came across new, and anything that arrived unapplied. The merged file is rebuilt and verified before delivery, so the balances have been recomputed from the merged transactions rather than carried over stale.
Contact us for a free assessment. Tell us roughly when the second file was started and whether anyone kept working in the original after that date.
Common Issues We Handle
- A new company file was started instead of continuing the existing one
- Months of data are stranded in a second file
- Invoices raised in the old file were paid in the new one
- Year-over-year comparisons stop at the point the file changed
- Your accountant is working from two files for a single tax year
How It Works
Tell us when the second file was started and which file should survive
Upload both files securely with the Admin password for each
We report the overlap, the split relationships, and the exact date boundary
You approve a fixed quote before any work begins
We merge, rebuild and verify, and return one continuous file plus a change report
If we are unable to complete the service, there is no charge. Your satisfaction is guaranteed.