Success Story
Revenue Hidden Behind a Reporting Book: Moving Two Sage Intacct Entities to QuickBooks Online Advanced Against a Hard Deadline
BLP, Inc. and its parent, Radius Group, LLC, had until January 31, 2026 to leave Sage Intacct, and their contract revenue only showed up under a dedicated reporting book. Here is how SaaS Direct took both entities live, with history from 2023, three days before the deadline.
Customer Overview
BLP, Inc. and Radius Group, LLC are based in Little Rock, Arkansas, and belong to BankLabs, a fintech group that builds cloud software for community banks. Radius Group, LLC is the parent, with history in Intacct from 2016 and three locations. BLP, Inc. is a C corporation with transactions from mid-2023, and is the main operating company.
Both entities ran in Sage Intacct in US dollars only, with General Ledger, Order Entry for contract invoices, Cash Management, and the Contracts module for contract lines and revenue recognition. Credit cards were tracked in Cash Management rather than Accounts Payable, and payroll was handled outside Intacct.
The Intacct subscription for both entities ended on January 31, 2026. They first contacted SaaS Direct on December 17, 2025.
Company Snapshot
- Location
- Little Rock, Arkansas
- Entities
- BLP, Inc.; Radius Group, LLC
- Industry
- Fintech
- Currency
- US dollars only
- Migration
- Sage Intacct → QBO Adv.
- Deadline
- January 31, 2026
The Challenge
In Intacct, contract revenue did not appear in a standard trial balance or general ledger report. It showed up only when the report was run under the “Contracts” reporting book. Run the extraction without it, and one entity’s trial balance showed no revenue for 2024 through 2026, years in which it had revenue.
Underneath sat a model difference. In Intacct, contracts are master records that transactions reference. In QuickBooks Online Advanced, revenue recognition runs through schedules on products and services linked to a deferred revenue account. In our assessment, those schedules apply going forward and cannot be linked back to historical transactions.
From: Sage Intacct
- Two entities: BLP, Inc. and Radius Group, LLC
- Contracts module with revenue recognition
- Revenue visible under a “Contracts” reporting book
- Departments and locations as dimensions
- Subscription ending January 31, 2026
To: QuickBooks Online Advanced
- One QBO Advanced company per entity
- Transaction history from 2023
- Departments as classes; locations kept
- Historical recognition as journal entries
- Live January 28, 2026
This is not unique to BLP. Intacct customers using the Contracts module can run into both problems: revenue that depends on a reporting book, and a contracts model with no direct QuickBooks Online equivalent. Both have to be settled before the extraction runs, not after.
What BLP needed
Done before the deadline
Both entities live in QuickBooks Online before the subscription ended on January 31, 2026.
Contract revenue intact
Revenue and receivables tying to Intacct, including contract revenue.
Each entity separate
Two companies, billed and run separately, as in Intacct.
Is this your situation?
Check where your Intacct revenue lives before you migrate
- You use the Intacct Contracts module for billing or revenue recognition
- Your revenue only reconciles under a specific reporting book
- You run more than one Intacct entity
- Your Intacct subscription has a fixed end date
If two or more apply, revenue mapping and extraction settings are the critical path of your migration, not the data load.
Designing the Migration
Five alternatives were considered and set aside between late December and January 23.
| Option considered | Why it was set aside |
|---|---|
| A standard two-cutoff plan with final delivery in March | The Intacct subscription ended January 31, too early for a March final delivery. |
| A temporary live file on January 26, full history in March | In the signed plan, then replaced on January 23 by a single release with history on January 28. |
| Recurring transactions as a stand-in for contracts | Our own early suggestion, superseded once revenue recognition schedules in QuickBooks Online Advanced were confirmed. |
| SaaS Direct building the deferred revenue setup in QuickBooks Online | Offered as extra scope. The client chose to set up recognition for open contracts itself, given contract nuances. |
| Merging duplicate customers and vendors | The client chose to rename duplicates rather than merge them. |
Chosen: one release, both entities, history from 2023
Each entity got its own QuickBooks Online Advanced company. Transactions from 2023 came across, extracted under the Contracts reporting book; historical revenue recognition came across as journal entries; departments became classes and locations stayed locations. The client took on recognition setup for open contracts itself. Proposed January 22 and agreed with the client on January 23.
What moved, and when
2016 to 2022
Radius Group history, handled outside the transaction load
2023 to Jan 16, 2026
Both entities, through the January 16 cutoff
January 28, 2026
Three days before the subscription ended
The Solution
The engagement ran on a profile of both entities, a fixed fee per entity, and a re-plan when the contracts problem surfaced. Five steps carried it:
Complexity Assessment
Both Entities Profiled
Before quoting, we profiled both Intacct entities once admin access was in place: counts, structure, dimensions and transaction volume.
Fixed Fee per Entity
Scored Separately
Each entity was scored and priced on its own complexity, with separate invoices per legal entity.
Extraction Packages
Reviewed with the Client
Packages for both entities, at a January 16 cutoff, were delivered January 19 and reviewed with the client on January 20, where the contract line and aging gaps surfaced.
Re-Extraction and Re-Plan
One Release, Not Two
On January 22 we re-extracted under the Contracts reporting book, delivered a written assessment of contracts versus QuickBooks Online, and proposed replacing the two-step plan with one release.
Tie-Out and Go-Live
Both Entities Live
The client tied both entities to Intacct and agreed the single release on January 23. Both went live January 28.
Commercial structure
Paid complexity assessment credited toward the project, then a fixed fee per entity, invoiced separately per legal entity, with milestone billing.
Obstacles, and How We Resolved Them
Seven things went wrong or needed a decision, two of them our own mistakes. How a migration partner handles those is a better guide than a clean story, so here they are in full.
Our first extraction missed contract revenue
The extraction ran without the Contracts reporting book, so contract revenue was missing from both entities’ packages and one entity’s AR aging did not reconcile. The client identified the reporting book on January 20 and the missing revenue on January 21.
Resolution. Re-extracted under the Contracts reporting book and re-delivered January 22. The client confirmed the tie-out on January 23.
Our first answer on contracts was wrong
On January 13 we told the client QuickBooks Online had no native contracts module and suggested recurring transactions. The client pointed out that QuickBooks Online Advanced has revenue recognition, and they were right.
Resolution. Corrected in writing on January 22, with a written assessment of what carries over and what does not.
Restricted Intacct access
Our Intacct user could initially see no modules or reports, and the parent entity was not visible until access was added.
Resolution. Upgraded to full admin the same day; the second entity was added December 23. BLP, Inc. was assessed December 23 and Radius Group, LLC December 26.
A slow start over the holidays
After our last update on December 31, the client did not hear from us until they chased on January 5.
Resolution. The staging database was already being built, and the agreement was signed January 6.
AP aging did not tie
Intacct’s AP aging did not match because credit cards were tracked in Cash Management, not Accounts Payable.
Resolution. Resolved by excluding credit card transactions, on the client’s direction.
Earlier history fell short
On January 21 the client flagged that summaries for Radius Group, LLC for 2016 to 2022 were missing, and our historical Excel package did not fully meet the client’s needs.
Resolution. We did not bill for the package. The earlier history is not part of the go-live described here.
Invoices and notices blocked
Our invoice emails were being filtered by the client’s email domain.
Resolution. The client unblocked our domain on January 23. We resent the invoices and they were paid.
Validation
The client ran the tie-out on January 23 and confirmed that net income tied for every period.
After go-live, the client reported that everything appeared in order and that they had not run across any issues related to the migration.
Checks before and at go-live
- Extraction checked against Intacct reports run under the Contracts reporting book
- AR and AP agings reviewed after the reporting book and credit card fixes
- Client tie-out on January 23: both entities and history agreed to Intacct
- At delivery: balance sheets and P&L, yearly and month over month
- At delivery: AR and AP agings compared
2023onward
Both entities: transaction history from 2023 through the January 16, 2026 cutoff; chart of accounts; customers, vendors and items; departments as classes and locations as locations; historical revenue recognition as journal entries.
2016 to 2022Radius history
Radius Group, LLC history for 2016 to 2022 was handled outside the transaction load. Left out: sales and purchase orders, inventory, payroll, and deferred revenue setup for open contracts, which the client took on itself.
The Results
Live Before the Deadline
Both entities have run in QuickBooks Online Advanced since January 28, 2026, three days before the Intacct subscription ended.
Contract Revenue That Ties
History extracted under the Contracts reporting book, with net income tying to Intacct for every period.
Full History About Five Weeks Early
Replacing the temporary file with one release delivered history from 2023 about five weeks ahead of the contracted date.
Two Clean Companies
Separate assessments, pricing, invoices and QuickBooks Online Advanced companies kept the two entities apart, as they were in Intacct.
Project timeline
Forty-two days from first contact to go-live, over the holidays, with a re-extraction and a re-plan in the last ten days.
The client took on revenue recognition setup for open contracts itself, and after go-live reported no issues related to the migration.
- Dec 17First contact; assessment approved
- Dec 22Intacct access upgraded to full admin
- Dec 23BLP, Inc. assessed
- Dec 26Radius Group, LLC assessed
- Jan 6Agreement signed
- Jan 16Extraction cutoff
- Jan 19Extraction packages delivered
- Jan 21Client flags missing contract revenue
- Jan 22Re-extraction; one release proposed
- Jan 23Client tie-out; one release agreed
- Jan 28Both entities live in QBO Advanced
- Jan 31Intacct subscription ends
Why It Worked
A Client Who Knew Their Intacct
The client identified the Contracts reporting book and the missing revenue within two days of the first package.
Fixing It Inside the Deadline
The re-extraction and a written contracts assessment went out the next day, with the subscription end date still ahead.
Replanning Around the Deadline
Dropping the temporary file for a single release removed a second cutover and delivered history about five weeks early.
Each Entity Treated as Its Own Project
Separate assessments, pricing, invoices and QuickBooks companies kept the two entities clean.
Clear Ownership of Revenue Setup
The client took on recognition for open contracts, where its contract knowledge mattered most.
Is Your Intacct Revenue Sitting in a Contracts Module?
Talk to us before your subscription end date. We will show you how your contracts and recognition map into QuickBooks Online Advanced.
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
Why can Intacct contract revenue be missing from a standard trial balance extract?
Because it may only appear under a reporting book. At BLP, contract revenue did not show in a standard trial balance or general ledger report; it appeared only when the report was run under the “Contracts” reporting book. Without it, one entity’s trial balance showed no revenue for 2024 through 2026.
How do you migrate the Intacct Contracts module to QuickBooks Online Advanced?
Extract under the reporting book that carries contract revenue, bring historical recognition across as journal entries, and set up recognition for open contracts in QuickBooks Online Advanced, where it runs through schedules on products and services linked to a deferred revenue account. At BLP, the client set up recognition for open contracts itself.
Can historical revenue recognition schedules link back to old QBO transactions?
No. In our assessment, revenue recognition schedules in QuickBooks Online Advanced apply going forward and cannot be linked back to historical transactions. That is why BLP’s historical recognition came across as journal entries.
How do you migrate two Intacct entities into separate QBO Advanced companies?
Treat each entity as its own project. BLP, Inc. and its parent, Radius Group, LLC, were assessed, priced and invoiced separately, and each went into its own QuickBooks Online Advanced company, with transaction history from 2023.
What if the Intacct subscription end date is weeks away?
Settle the reporting book and the release plan early, and cut steps that do not fit the date. BLP first contacted us on December 17, 2025, with the subscription ending January 31, 2026. Replacing a temporary live file plus a later history load with one release took both entities live on January 28, three days before the deadline.
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.
Is Your Intacct Revenue Sitting in a Contracts Module?
Talk to us before your subscription end date. We will show you how your contracts and recognition map into QuickBooks Online Advanced. The destination in this story is QuickBooks Online Advanced, not Intuit Enterprise Suite.
Related: Sage Intacct migrations · QuickBooks Online migrations · All success stories · Treatment Advocacy Center story · Metro Denver Homeless Initiative Intacct story · Sage Intacct exit checklist · Enterprise multi-entity migrations
Book a Sage Intacct 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.