Success Story
A System They Didn’t Own: Moving an Independent School off Sage Intacct on a Fixed Exit Date
The Classical Academy of Sarasota did not own the Sage Intacct instance that held its books. Its outgoing accounting firm did, under that firm’s Sage partner agreement, and the school had 60 days to get out. Here is how SaaS Direct moved the school to QuickBooks Online Advanced from source data that was still changing.
Customer Overview
The Classical Academy of Sarasota (TCA) is a PreK-12 independent school in Sarasota, Florida, founded in 2014. It is a nonprofit with one entity, US dollars only and a July to June fiscal year. The school also carries campus bond financing with its own reporting obligations.
Accounting in Intacct covered the general ledger, receivables, payables, bills and invoices. Around it sat Ramp for cards and payables, Square through a Synder sync, FACTS for tuition, ADP for payroll (posted as summary journals) and Martus. The books had been kept by an outsourced accounting firm, and the school was moving to a new firm at the same time as the migration.
The Intacct instance was held by that outgoing firm under its Sage partner agreement. The school had no administrator rights and a 60-day window from mid-May to leave, with the Intacct exit set for mid-July 2026.
School Snapshot
- Location
- Sarasota, Florida
- Organization
- PreK-12 independent school (nonprofit)
- Fiscal year
- July to June
- Migration
- Sage Intacct → QBO Adv.
- Deadline
- Intacct exit, mid-July 2026
The Challenge
Most migrations start with an administrator login. This one could not. The outgoing accounting firm held the Intacct subscription under its Sage partner agreement and would not delegate administrator control. It provisioned named business users instead, and access landed about two weeks after the school decided to proceed.
Once inside, the source would not hold still. Card transactions were being pushed into Intacct for prior periods after the cutoff we had planned around, so an extraction taken at March 31 would no longer match what Intacct showed. And the books had gaps of their own: the AP aging did not tie to the balance sheet, bank reconciliations were incomplete, and a Square sync had been left on manual.
From: Sage Intacct
- Instance held by the outgoing accounting firm
- No administrator rights for the school
- Three dimensions: campus, projects, departments
- Ramp, Square, FACTS and ADP feeding the books
- Exit window: 60 days from mid-May
To: QuickBooks Online Advanced
- Administered by the school
- January 2025 onward at transaction level
- Original invoice and bill types preserved
- Open AR and AP as open items
- Earlier history in a reconciled Excel archive
This is not unique to TCA. Any organization whose Sage Intacct instance sits under an outgoing partner’s agreement will meet the same three constraints: limited access, a fixed exit date, and books that the previous firm may not have finished closing.
What the school needed
Control of the new system
Full authority over the QuickBooks Online instance, which the school never had in Intacct.
Make the bond reporting date
The migration could not push the school past its bond reporting deadline.
Keep full history
An archive back to 2014, so Intacct could be fully decommissioned.
Is this your situation?
Check who holds your Intacct instance before you pick a migration date
- Your Sage Intacct subscription runs through a partner or outgoing firm
- You do not have administrator rights in your own instance
- Card or payment integrations still post into periods you consider closed
- Your exit date is set by a contract, not by your project plan
If two or more apply, access and cutoff design are the critical path of your migration, not the data load.
Designing the Migration
Seven alternatives were considered and set aside. Most were settled at scoping; the March 31 historical cutoff failed in mid-June, and the delay option was the school’s own decision on July 3.
| Option considered | Why it was set aside |
|---|---|
| Seven or more years of history at transaction level | QuickBooks Online API throttling and error handling across thousands of calls, at a cost with no matching operational benefit. History before 2025 went to the archive instead. |
| Journal entries only | Invoices and bills would lose their original transaction types. |
| Opening balances only | Not a fit for a school that needs to look across a full enrollment cycle. |
| Open AR and AP as one opening journal entry | Replaced by open items from the aging reports, so the subledgers tie out. |
| Intacct projects as customer-linked sub-customers | No standard migration path; everything except the parent-child structure would have needed manual custom fields. |
| A historical cutoff at March 31, 2026 | Card transactions were back-posted into periods after that date, so the extraction would no longer reconcile to Intacct. |
| Delay the blackout to clean the source books first | Rejected by the school on July 3: the December 31, 2025 figures were validated, a delay risked slipping further, and the bond reporting date had to be met. |
Chosen: two cutoffs, transaction history from 2025, a reconciled archive
The historical load ran through December 31, 2025 and was validated and approved on its own. The school’s last working day in Intacct was July 3; the final extraction ran July 4 and the delta load was delivered July 13. Projects became QuickBooks Online classes with their parent-child structure intact. One of the three Intacct dimensions did not carry over, because QuickBooks Online offers two.
July 2014 to Dec 2024
Excel archive: all transactions and yearly trial balances, reconciled
Jan to Dec 2025
First cutoff load: frozen history, delivered June 29
Jan 1 to July 3, 2026
Final delta: extracted July 4, delivered July 13
The Solution
The engagement ran on a paid assessment, an expedited plan against the exit date, and two cutoff loads around a blackout. Five working disciplines carried it:
Complexity Assessment
Inside Business-User Access
Before quoting, SaaS Direct profiled the Intacct company through the business-user access we were given: 195 accounts, 3,873 customers, 1,655 vendors, 6 campus locations, 167 projects, 13 departments and an estimated 60,000+ transaction lines from January 2025. The result was a fixed-fee quote with scaled options.
Expedited Plan
Against the Exit Date
The school chose an expedited schedule at a premium, signed June 3 and kicked off the same day, with client feedback on each milestone expected within one business day.
Extraction Package
With Written Discussion Points
The first extraction package went to the client June 10 with written discussion points on dimensions, duplicate names, blank record types and the AP aging. It was re-issued June 18 on the new December 31, 2025 cutoff.
Two Cutoffs and a Blackout
Frozen History, Then Final Delta
The first cutoff load was delivered June 29. July 3 was the last working day in Intacct, the final extraction ran July 4, and the blackout held until the final load on July 13. Integration syncs were held until after the blackout.
Written Root Cause
For Every Variance
After go-live, each variance the client or its new accounting firm raised was traced and answered in writing, with the fix, if any, located in the system that needed it.
Commercial structure
Paid complexity assessment, then a fixed-fee quote on an expedited schedule. Milestone billing tied to client approval of the extraction package and of the QuickBooks Online test environment. The historical archive was a separately priced add-on.
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.
No administrator access to the source
The outgoing firm would not delegate admin rights because the subscription sat under its Sage partner agreement. The first invite could not be found on our side, and access landed May 21, about two weeks after the school decided to proceed.
Resolution. We scoped the extraction to business-user access across the modules and reports we needed, and ran the assessment inside that.
The historical cutoff moved
In mid-June we found card transactions posted into Intacct for periods after the planned March 31 cutoff. The extraction package no longer matched the live system.
Resolution. Cutoff reset to December 31, 2025 on June 17, and the extraction package re-issued June 18.
We slipped a week
The extraction package discussions took more rounds than planned, the cutoff changed, and QBO access was still being set up. We reset the milestones on June 23; the client’s package review arrived June 26.
Resolution. First load delivered June 29, ahead of the revised July 2. Final delivery July 13, one week after the July 6 contract date and before the Intacct exit.
The source books were not clean at cutover
At the July 3 decision point, bank reconciliations were incomplete and a backlog of roughly 180 Square transactions had not synced into Intacct.
Resolution. The school chose to freeze on schedule and clean up in QuickBooks Online afterwards with its new accounting firm, to protect its bond reporting date. Syncs were held until after the blackout.
Apparent variances after go-live
A checking-account balance looked off because the report had been run at July 14 instead of the July 3 cutoff. Another gap was amortization of loan costs, which the Intacct report presented differently and QuickBooks Online correctly shows as a contra fixed asset.
Resolution. Re-run as of July 3, spot-checks matched. The balance sheet balanced and open AP matched the source.
A Statement of Activities variance
Two accounts, In-Kind Expense (one transaction) and Sales Tax Paid (129 transactions), were in both systems but left out of the school’s customized Intacct Statement of Activities.
Resolution. Root cause documented July 21: a report-layout setting in Intacct, not a migration error. A reported class double-count was likewise report behavior; P&L by Class reconciles.
Vendor tax details
The client expected W-9 and TIN details to come across. Attachments were outside the agreed scope, and QuickBooks Online has no standard field for 1099 form type.
Resolution. 1099 flags and Tax IDs populated on July 28. The client confirmed it was fine with what was brought over.
Validation
Where the Intacct AP aging did not reconcile to its own balance sheet, we traced the underlying transactions and adjusted: three vendors at December 31, 2024, and one vendor at December 31, 2025.
The client’s new accounting firm ran its own tie-outs after the final load, including revenue, salaries and the expense groups on the Statement of Activities, which is how the report-layout gap was isolated to two accounts.
Checks across the two loads
- Trial balance, Intacct against QBO, at December 31, 2024
- Balance sheet at each fiscal year-end
- Income statement at each fiscal year-end
- AR and AP agings at December 31, 2024, December 31, 2025 and the final cutoff, July 3, 2026
- P&L by Class, reconciled after go-live
- Archive: yearly trial balances recalculated from extracted transactions and reconciled to Intacct
18months
January 1, 2025 through July 3, 2026 at transaction level, with original transaction types; open AR and AP as open items; chart of accounts, customers, vendors and dimensions (as locations and classes); 1099 flags and Tax IDs.
10.5years
July 1, 2014 through December 31, 2024: all Intacct transactions and yearly trial balances in an Excel package, reconciled with no exceptions. Attachments were outside the agreed scope.
The Results
Off Intacct Before the Exit
July 3 was the school’s last working day in Intacct. The final extraction ran July 4 and the final load was delivered July 13, before the mid-July exit.
A System the School Controls
TCA runs its books in QuickBooks Online Advanced with full administrator authority, which it never had in Intacct.
Full History, Split by Use
January 2025 onward at transaction level, where it gets used. The ten and a half years before that in a reconciled archive, so Intacct can be fully decommissioned.
Every Variance Traced
After go-live the balance sheet balanced and open AP matched the source. Each variance raised was traced to report dates, Intacct report configuration or agreed scope, not to errors in the migrated data.
Project timeline
Forty days from signed contract to final load, against an exit date set by someone else’s contract. The final load landed one week after the contract date and before the Intacct exit.
Source cleanup the school chose to defer, the bank reconciliations and the Square backlog, sits with the school and its new accounting firm.
- April 29First contact
- May 8School decides to proceed
- May 21Business-user access to Intacct granted
- May 27Assessment findings and fixed quote
- June 3Contract signed; kickoff
- June 10Extraction package and discussion points
- June 17Historical cutoff reset to Dec 31, 2025
- June 23Milestones reset
- June 29First cutoff load delivered
- July 3Last working day in Intacct
- July 13Final load delivered (plan: July 6)
- July 16Reconciled archive delivered
- July 281099 flags and Tax IDs added
Why It Worked
Working Inside the Access We Had
We scoped the extraction to business-user rights rather than waiting on an administrator login that was never coming.
A Frozen Historical Cutoff
Validating 2025 on its own meant the final delta only had to reconcile six months, not eighteen.
Letting the Client Make the Trade-Off
On July 3 the school had the facts to choose between cleaner source books and its bond reporting date. It chose the date, knowingly.
Migrated and Archived Kept Separate
Transaction-level history where it gets used; a reconciled archive for the rest.
Root Cause in Writing
Every post-go-live variance got a written explanation, including the ones that turned out not to be migration issues.
Is Someone Else Holding Your Intacct Instance?
If a partner or outgoing firm controls your Sage Intacct subscription, we will work through access, cutoffs and archive scope with you before your exit window starts.
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
What if your Sage Intacct instance is held by an outgoing accounting firm?
Plan around the access you can get and the date the instance goes away. At The Classical Academy of Sarasota, the outgoing firm held Intacct under its own Sage partner agreement, would not grant administrator rights, and the school had 60 days to get out. We worked from the named business users it provisioned instead, and the school moved to QuickBooks Online Advanced in 40 days from signed contract to final data load.
Can you migrate without Intacct administrator rights?
In this case, yes. The outgoing firm would not delegate administrator control, so the extraction was scoped to the named business-user access it did provide. Whether that is enough for another organization depends on which modules and reports those users can reach, so it is worth checking before the scope is fixed.
How do you handle card postings into “closed” periods at cutoff?
Move the cutoff rather than reopen what was validated. At the school, card transactions were still being pushed into Intacct for periods after the planned March 31 cutoff, so we reset the historical cutoff to December 31, 2025, validated that load on its own, and carried January 1 to July 3, 2026 in a final delta.
Should older history go to QBO or a reconciled archive?
Split it by how it will be used. The school kept 18 months of transactions in QuickBooks Online Advanced, from January 2025, and moved July 2014 to December 2024 into a reconciled Excel archive with yearly trial balances: 10.5 years in all.
How fast can an independent school exit Intacct on a fixed contract date?
The Classical Academy of Sarasota took 40 days from signed contract to final data load, inside its exit window. The final load was delivered July 13 and the reconciled archive followed on July 16. Timing for another school depends on access, cutoffs and how much history it needs.
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 Someone Else Holding Your Sage Intacct Instance?
Talk to us before your exit window starts. Access, cutoffs and archive scope are decided in the first week, not the last. The destination in this story is QuickBooks Online Advanced, not Intuit Enterprise Suite.
Related: Sage Intacct migrations · QuickBooks Online migrations · All success stories · Metro Denver Homeless Initiative Intacct story · Treatment Advocacy Center story · BLP Intacct story · Sage Intacct exit checklist
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.