Accounting Software Implementation: The CFO’s Cutover Playbook

Accounting Software Implementation: The CFO’s Cutover Playbook

Woosung Chun

CFO

Woosung Chun is the CFO of DualEntry with experience in corporate finance, accounting, strategy, and acquisitions. He previously grew from scratch and led the M&A and Finance teams at Benitago, where he completed more than 12 acquisitions in 2 years. He graduated with a BS from NYU Stern. At DualEntry, Woosung writes about AI in accounting, revenue recognition, foreign currency accounting, hedge accounting, and ERP modernization for finance teams navigating complex, multi-entity environments.

Last updated

November 6, 2026

Reviewed by

Do San (Justin) Myung

Do San (Justin) Myung

Expert Accountant & Former Consulting CFO

Justin (Do San Myung) is Expert Accountant at DualEntry with 20+ years of hands-on experience managing general ledgers, financial close processes, and ERP implementations for mid-market and enterprise companies. As a former Consulting CFO and Controller, he has personally overseen month-end closes, SOX compliance programs, and multi-entity consolidations across technology, manufacturing, and services industries. Justin specializes in transforming manual accounting workflows into automated, AI-driven processes.

Contents

What is accounting software implementation?

.avif)

Accounting software implementation is everything that happens between signing the contract and trusting the new system's first close. It covers chart-of-accounts design, configuration, data migration, testing, training, and cutover.

Implementation timeline by complexity tier

Tier Profile Realistic timeline Gating factor
1 Single entity, standard COA, no integrations 4–8 weeks Data cleanup ownership
2 Single entity + billing/payroll/AP integrations, ASC 606 config 3–5 months Integration testing & rev-rec rules
3 Multi-entity, consolidation, FX, historical detail migration 6–9 months Intercompany mapping & tie-outs

What implementation really costs

Implementation cost matrix by company stage

Cost line Leaving QuickBooks (Tier 1) Mid-market single entity (Tier 2) Multi-entity (Tier 3)
Partner / implementation fees $0–$15k $25k–$75k $75k–$250k+
Internal finance hours 100–200 hrs 300–600 hrs 800–1,500+ hrs
Integrations / middleware $0–$5k $10k–$40k $40k–$100k+
Hidden (data transform, parallel run) 5–10% of total 10–15% 15–20%

Fixing the chart of accounts before you migrate

Chart of accounts design determines post-implementation reporting quality, which makes it one of the highest-leverage decisions in the entire project.

Data migration: how much history should you bring over?

Default to migrating the opening trial balance plus two years of monthly trial balances. Bring transaction-level detail only for open AR and AP items.

GL history migration: decision table

Depth What moves Choose when Cost/effort
Opening TB only One trial balance at cutover + open AR/AP items Clean break, weak legacy data, Tier 1 Low
Monthly TBs (2 years) Comparative monthly balances, no transactions Board/lender comparatives needed (the default) Medium
Full transaction detail Line-level history, mapped to new COA Audit/diligence demands, or AI-native system trains on it High — price it before promising it

Go-live and the parallel run

Should you run old and new accounting systems in parallel? Yes – but agree the end point before you start.

Go/no-go criteria at cutover

Criterion Standard Owner
Subledger tie-outs AR/AP/FA equal control accounts to the cent Controller
UAT Full O2C and P2P cycles passed on real company transactions Process owners
Training Every daily user completed role tasks unassisted Implementation lead
Rollback plan Documented; legacy system frozen but restorable CFO
Parallel-run exit 2 consecutive closes within variance threshold CFO + auditor

Audit readiness: how to be prepared for every difficult question

A system conversion is an ICFR event – a change to your internal controls over financial reporting – and your auditors will test the conversion itself.

Expect these 4 asks:

How AI-native systems change the playbook

In a legacy implementation, historical data is a cost to minimize. In an AI-native implementation, it's an asset.

Accounting software implementation checklist

Here’s the whole playbook we’ve walked through above, compressed into a single screen. If every line in here can be assigned an owner and a date, your team’s ready.

Implementation to-dos, phase by phase

Phase Non-negotiables
Before Requirements matrix · COA redesign · Old-to-new account mapping · Data-cleanup owner named
During Sandbox configuration · Integrations built · Migration depth chosen · UAT on real transactions
Cutover week Legacy freeze · Final TB export · Opening journal · Subledger tie-outs · Bank feeds switched
After Parallel-run exit test · 30/60/90 reviews · Conversion workpapers filed · Automation backlog

Conclusion

When an implementation fails, it’s less about software and more about unowned decisions. If your next implementation is Tier 2 or 3, see how DualEntry’s AI-native system makes it easier with a 24-hour data migration, a CPA-led onboarding, and $0 implementation fees.

Accounting Software Implementation FAQs

What is accounting software implementation?

It's the process of configuring, migrating data into, testing, and cutting over to a new accounting system — everything between contract signature and the first month-end close that you trust.

How long does accounting software implementation take?

An implementation takes 4 to 8 weeks for a single-entity company with a standard COA, 3–5 months if you need to factor in integrations and revenue-recognition configuration, and 6–9 months if multi-entity consolidation is needed.

How much does accounting software implementation cost?

As a rule of thumb, budget roughly 1–2x first-year license cost all-in for a Tier 1–2 implementation: covering partner fees, internal finance hours, and integrations.

What are the steps of accounting software implementation?

Requirements and COA redesign, system configuration, data migration, integration build, user acceptance testing, training, cutover at a month boundary, and a parallel run with defined exit criteria — followed by 30/60/90-day reviews.

Should you run old and new accounting systems in parallel?

Yes for multi-entity or integration-heavy implementations, but only with exit criteria.