Success Story
Two Sets of Books, One Company: Merging Two QuickBooks Enterprise Files into QuickBooks Online Advanced
Paint One merged legally in 2022 but kept two sets of books in QuickBooks Enterprise. Here is how SaaS Direct combined them into one QuickBooks Online Advanced company, rebuilt jobs as projects and restored job profitability reporting.


Customer Overview
Paint One is a drywall and painting subcontractor based in Matthews, North Carolina, with divisions in North Carolina, South Carolina, Tennessee, Georgia and Alabama. Its customers are homebuilders, and it tracks work by job and by geographic class.
Paint One, Inc. and Paint One Coastal merged legally in 2022 but kept separate books in two QuickBooks Enterprise desktop files, on a calendar year and in US dollars. The client suspected one of the files was corrupt.
The team runs the business on job profitability reporting. Whatever the new structure looked like, that report had to work on day one.
Company Snapshot
- Location
- Matthews, North Carolina
- Divisions
- NC, SC, TN, GA and AL
- Customers
- Homebuilders
- Source
- Two QuickBooks Enterprise files
- Migration
- QBE → QBO Adv.
- Live
- August 10, 2026
The Challenge
Two QuickBooks Enterprise files had grown apart for years. Their charts of accounts used some of the same numbers for different accounts, and different numbers for the same account. Merging them needed a rule for every conflict, agreed before any data moved.
Jobs were the second problem. QuickBooks Enterprise treats jobs as a first-class entity under each customer; QuickBooks Online has no jobs concept. Jobs had to become QuickBooks Online Projects linked to their customers, or job profitability reporting would not work.
From: QuickBooks Enterprise
- Two desktop files, one per former company
- Separate charts of accounts
- Jobs under customers for job tracking
- Geographic classes in each file
- A file with suspected corruption
To: QuickBooks Online Advanced
- One company for the merged business
- One chart of accounts, conflicts resolved
- Jobs rebuilt as QBO Projects
- Geographic classes from both files
- Live daily from August 10, 2026
This is not unique to Paint One. Any business that merged companies but kept separate QuickBooks Enterprise files will meet the same two issues: conflicting charts of accounts and a jobs structure QuickBooks Online does not have. In our experience, both belong in the design, before extraction.
What Paint One needed
One set of books
A single company in QuickBooks Online Advanced for the merged business.
Jobs and profitability
Work tracked by job, with job profitability reporting working.
Numbers that tie
Balances that agree to both source files, with legacy issues resolved.
Is this your situation?
Merged the companies but not the books?
- Your companies merged but your books did not
- You run jobs under customers in QuickBooks Enterprise
- Your job profitability report drives decisions
- Your desktop file has shown signs of corruption
If two or more apply, chart of accounts rules and the jobs design are the critical path of your migration, not the data load.
Designing the Migration
Seven alternatives were considered and set aside.
| Option considered | Why it was set aside |
|---|---|
| A consolidated QuickBooks Enterprise file as the end state | The client was moving to QuickBooks Online Advanced; merging on the desktop would have kept the old platform. |
| Importing the data themselves from spreadsheets | Not practical at this volume, with jobs, classes and two charts of accounts. |
| A job-costing add-on | The team uses job profitability, not job costing, so QuickBooks Online Projects covered the need. |
| A QuickBooks Online location for each former company | Left out after the client confirmed it would not report by former company. |
| Our proposed correcting entry for a legacy difference | The client, on its CPA’s advice, chose to offset through a credit card account instead. |
| Bringing 2024 history into QuickBooks Online | The client’s CPA recommended starting from 2025; earlier years stay in the two desktop files. |
| Converting estimates to linked invoices | The source files had no links between estimates and invoices to carry over. |
Chosen: one company, jobs as projects, two loads
Both files merged into one QuickBooks Online Advanced company from January 1, 2025. Chart of accounts conflicts went to the Paint One name: the same number with a different name, and a different number with the same name, both resolved to Paint One. Jobs became QuickBooks Online Projects, geographic classes from both files carried over, and a final load caught up activity to July 31, 2026.
What moved, and what stayed on the desktop
2024 and earlier
Prior years stay in both QuickBooks Enterprise files
Jan 1, 2025 to Mar 31, 2026
Both files merged into one company
Apr 1 to Jul 31, 2026
Catch-up before go-live
The Solution
The engagement ran on an assessment of both files, a written extraction package, agreed conflict rules and two loads. Five steps carried it:
Discovery and Assessment
Both Files Profiled
Discovery on April 14 and a complexity assessment of both QuickBooks Enterprise files on April 21.
Fixed-Fee Scope
Merge, Jobs and Two Loads
Agreement sent and deposit paid on May 14, covering the merge, jobs to projects and two loads.
Extraction Package
Reviewed and Revised
Delivered June 12, reviewed with the client on June 16 and revised on June 23.
Chart of Accounts Roll-Up
Conflict Rules Agreed
Rules for every chart of accounts conflict were agreed with the client on July 7, before the first load.
Two Loads and Go-Live
Test, Then Catch Up
First load delivered July 23, final load August 6, and Paint One live daily in QuickBooks Online Advanced from August 10.
Commercial structure
Paid complexity assessment of both files, then a fixed-fee scope covering the merge, jobs to projects, and two loads with a final catch-up. After go-live we added a PO field, outside the original scope, and re-loaded missed memo detail.
Obstacles, and How We Resolved Them
Seven things went wrong or needed a decision. How a migration partner handles those is a better guide than a clean story, so here they are in full.
Job profitability came up blank
During the final freeze, before go-live, the job profitability report showed no data. It is the report the team runs the business on.
Resolution. Found and fixed the next day, August 5.
Details we missed in extraction
Journal entry memos and vendor bill line descriptions did not come across.
Resolution. Re-loaded on August 13, when we also added a PO custom field outside the original scope.
Flags that did not carry over
Inactive flags on some customers and vendors did not carry over after the first load, and some sub-customers were missing the bill-with-parent setting.
Resolution. Customers corrected July 28, vendors July 29 and bill-with-parent August 5, all before go-live.
A reset at the start
After the assessment, the client deactivated about 10,000 customers, so extraction restarted from new files received May 27.
Resolution. Extraction package delivered June 12.
A crash-damaged entry
A large entry in the source had been damaged by a QuickBooks Enterprise crash, according to the client.
Resolution. Resolved on the client’s instructions, with its CPA’s input, before the final load.
Differences in the source books
One payment was posted only to the AR aging, and the opening balances carried a small difference.
Resolution. The payment moved to a miscellaneous customer on the client’s instruction, and the balance sheet was brought into balance before go-live.
A late start in QuickBooks Online
Access to the QuickBooks Online company came on July 9, after a vacation and a platform outage.
Resolution. The timeline moved two weeks; the first load was delivered July 23, ahead of the revised July 27 date.
Validation
AR and AP tied after the first load, and every load was checked against both source files. An income amount posted to the wrong account was reclassified, and a small difference was traced to two accounts merged in the chart of accounts roll-up.
On August 11 the client confirmed that validation of the numbers was complete.
Checks at each load
- AR and AP tied after the first load
- Trial balance at December 31, 2024
- Balance sheet and income statement at each fiscal year-end
- AR and AP agings at December 31, 2024 and March 31, 2026 (first load)
- AR and AP agings at July 31, 2026 (final load)
2025onward
One company for both former files: transactions from January 1, 2025 through July 31, 2026; one merged chart of accounts; customers, vendors and items; jobs as QuickBooks Online Projects; geographic classes from both files; open estimates.
2024and earlier
Kept: 2024 and earlier years in the two QuickBooks Enterprise desktop files. Left out at the client’s request: a QuickBooks Online location for each former company. Estimates were not linked to invoices, as the source had no links.
The Results
One Company, Four Years On
Paint One runs as one company in QuickBooks Online Advanced, live daily since August 10, 2026, four years after its legal merger.
Job Profitability Working
Jobs are QuickBooks Online Projects linked to their customers, and the client confirmed job profitability reporting works.
One Chart of Accounts
Every numbering and naming conflict between the two files resolved by a rule agreed before the first load.
Final Load Ahead of Go-Live
The final load was delivered August 6, ahead of the August 10 commitment, and the client completed validation of the numbers.
Project timeline
The project restarted once, when the client cleaned up about 10,000 customers after the assessment, and moved two weeks when access to the new company came late. The final load still arrived ahead of go-live.
Two misses of our own, a blank job profitability report and missing memo detail, were fixed within days.
- Apr 14Discovery
- Apr 21Complexity assessment of both files
- May 14Agreement sent; deposit paid
- May 27Customer cleanup; extraction restarts
- Jun 12Extraction package delivered
- Jun 23Revised package after review
- Jul 7Chart of accounts roll-up agreed
- Jul 23First load delivered
- Jul 31Final backup
- Aug 6Final load delivered
- Aug 10Live daily in QBO Advanced
- Aug 13Memos re-loaded; PO field added
- Sep 3Closure check-in
Why It Worked
Rules Before Data
Agreeing chart of accounts conflict rules up front made the merge predictable.
Designing for How They Work
Projects and job profitability, not job costing, matched how the team runs jobs.
The Client and Its CPA in the Loop
Legacy differences were resolved on the instructions of the people who own the books.
Two Loads
A first load for testing meant the final load only had to add April to July activity.
Fixing Our Misses Fast
The blank report was fixed the next day, and missed detail was re-loaded within a week of go-live.
Still Running Two Sets of Books After a Merger?
Talk to us about combining your QuickBooks Enterprise files into one QuickBooks Online Advanced company, with your jobs and classes intact.
Download
Download the Case Study
Keep this story as a PDF. The case study summary is built for sharing with your team; the full case study covers every design decision, obstacle and validation step.
Case Study Summary
The problem, the solution, how we validated it and the result, on two pages.
Download PDFFull Case Study
The complete account: starting position, the options we set aside and why, obstacles and how we resolved them, validation and timeline.
Download PDFFrequently asked questions
How do you merge two QuickBooks Enterprise company files into one QBO Advanced company?
Agree a rule for every chart of accounts conflict before any data moves, then load both files into one company. Paint One merged its two QuickBooks Enterprise files into one QuickBooks Online Advanced company from January 1, 2025, with jobs rebuilt as projects and geographic classes from both files carried over, in a first load and a final catch-up load.
What happens to QuickBooks Desktop jobs in QuickBooks Online?
QuickBooks Online has no jobs concept, so jobs have to become QuickBooks Online Projects linked to their customers. At Paint One, every job was rebuilt as a project under its customer, which kept job profitability reporting working.
How do you resolve conflicting charts of accounts across two QBE files?
Write the rules down and agree them first. Paint One’s two files used some of the same numbers for different accounts and different numbers for the same account. Both kinds of conflict were resolved to the Paint One name, under rules agreed with the client on July 7, before the first load.
Can job profitability reporting work after QBE → QBO Advanced?
Yes. With jobs rebuilt as projects, Paint One confirmed job profitability reporting works in QuickBooks Online Advanced. The report came up blank during the final freeze, before go-live; we found and fixed the cause the next day.
Should pre-2025 history stay in the desktop files?
For Paint One, yes. Its CPA recommended starting from 2025, so transactions from January 1, 2025 came across and 2024 and earlier stay in the two QuickBooks Enterprise desktop files. Whether that fits another business is a decision for its accountant.
About SaaS Direct
SaaS Direct is a financial systems migration specialist helping businesses and accounting firms transition between legacy and modern platforms. With a proprietary migration code repository spanning 88+ platforms and a disciplined delivery methodology, SaaS Direct handles the technical complexity of accounting transitions so finance teams and advisory firms don’t have to.
Still Running Two Sets of Books After a Merger?
Talk to us about combining your QuickBooks Enterprise files into one QuickBooks Online Advanced company, with your jobs and classes intact. The destination in this story is QuickBooks Online Advanced, not Intuit Enterprise Suite.
Related: QuickBooks Enterprise migrations · QuickBooks Online migrations · All success stories · Construction ERP migrations · Data migrations
Book a QuickBooks Enterprise Migration Review
Pick a time that suits you. You will speak with a migration lead who has moved this exact path, not a call center.
