Sage Intacct· Cutover
Sage Intacct cutover and go-live
Cutover is the planned move from the legacy system to Sage Intacct: the freeze, the final loads, the opening balances and the go/no-go call. superglue's agent writes the runbook from the project and the rehearsal, runs the final and delta loads with the tested tools, and reconciles before you and the client make the call.
How this step works
What the agent does
- Writes the cutover runbook with tasks, owners and timings from the rehearsal.
- Runs the final and delta loads with the tools tested in the rehearsal.
- Reconciles opening balances and open items against the legacy system.
- Prepares the go/no-go summary with the open issues.
What you decide and approve
- The cutover date and the freeze window.
- Go or no-go, together with the client.
- The fallback plan if the answer is no.
What the client gets
- A cutover runbook.
- A signed go-live reconciliation.
What makes a Sage Intacct cutover work
- 01
Freeze the source and agree go/no-go criteria
Agree the freeze window and the checks that must pass before cutover weekend, such as the trial balance per entity and the AR and AP aging.
- 02
Close the books before the go-live date
After history and opening balances load, close the books through the day before go-live. Closing the GL also closes AP and AR, so no one posts into conversion periods.
- 03
Load outstanding bank items for the first reconciliation
Enter outstanding checks and deposits as initial open items, with the day before go-live as the cut-off date. The first bank reconciliation then starts from the legacy balance.
- 04
Check the first payment run
Bills paid in the legacy system during the freeze must be closed in the delta load. Review the first payment run in Sage Intacct so no bill is paid twice.
“We do 40+ Sage Intacct implementations a year, and data migration used to take half our budget on every project. superglue turned our biggest cost center into something we can scope in hours, not weeks.”
Frequently asked questions
What makes a Sage Intacct cutover go well?
Freeze the source and agree go/no-go criteria; Close the books before the go-live date; Load outstanding bank items for the first reconciliation; Check the first payment run. The agent runs the final loads with the tools tested in the rehearsal.
Who makes the go-live call?
You and the client do. The agent prepares the reconciliation and the list of open issues for the go/no-go meeting.
How does superglue work with our consultants?
superglue works alongside your team. The agent takes on the repetitive work, such as reading documents, drafting, mapping, loading and reconciling. Your consultants keep the client relationship and the decisions, and they approve every change to a client system.
Can we use our own implementation method?
Yes. Write your firm's method as a playbook, and every consultant and every session follows it. The documents the agent produces carry your firm's branding.
Which systems can we migrate from into Sage Intacct?
Common sources are QuickBooks, Sage 50, Sage 100 and Sage 200, Microsoft Dynamics GP, Xero and spreadsheets. The agent also reads Excel, CSV and XML exports and most systems with an API or a database.
Is client data safe?
superglue holds a SOC 2 Type 2 report and works under GDPR. Credentials are encrypted with AES-256. On the Enterprise plan, superglue can run on your own infrastructure.
How do we start?
Start with one live Sage Intacct project. Connect the client's systems, give the agent the statement of work, and run the first steps together with us.