How migration works
Migrate to Light.
4–6 weeks, with a dedicated implementation team. Here’s how it works, and how four different companies did it.
Timeline
4–6 weeks, done alongside your team.
Team
A dedicated implementation team and account manager run it with you.
Control
Every migrated record is reviewed by your team before it goes live.
Why is a Light migration faster?
Migrating to a typical ERP means syncing yet another tool into an already tangled stack. Migrating to Light means removing tools, and removing things is faster than adding them.
A typical ERP migration
- + AP
- + Spend
- + CRM
- + Bank feeds
- + Tax
One more system to sync
Migrating to Light
APSpendCRMBank feedsTax
One system, natively
Typical ERP
6–18 monthsvia a system integratorLight
4–6 weeksHow the migration platform works
Light’s migration platform is purpose-built for exactly this move, off NetSuite, SAP, or whatever mix of tools you’re running today. It’s agents, the same technology that runs your books afterward, doing the mechanical work, with your team and ours reviewing everything before it counts.
“ERP migrations are painful as a general rule. You can have a less painful experience or a very painful one. The Light team answered us at very late hours of the night, which matters when you are three people running a project this size.”
Four different starting points, four different migrations
There’s no single “typical” migration, because there’s no single kind of mess a finance team is climbing out of. These are real ones.
Day 12Day 5Tillo8 ledgers and 2 failed ERP implementations before Light.
SevenOneAll Gravy6 years of transaction history reconciled and moved. Closes in 5 days on a team of 3.
ThreeOnePaebblThree separate ERP general ledgers across the group, replaced with one global platform.
ThreeOneOfficegurue-conomic, a decades-old consolidation tool, and custom import tooling, live on one platform within a week of signing.
Three steps, from your old system to your first close
- 1
Connect
The platform pulls your data directly from the source system, NetSuite, SAP, Business Central, Sage Intacct, QuickBooks, Xero, or whatever you’re on today.
- 2
Validate, clean & map
Agents check the data for gaps and duplicates, then map it to the right place in Light’s ledger.
- 3
Review & approve
Everything surfaces for your team to review and sign off before go-live, with your account manager alongside you.
Frequently asked questions
How long does migration actually take?
4–6 weeks, with a dedicated implementation team and account manager included. The exact timeline depends on what you’re moving from: see the specifics for NetSuite, SAP, Business Central, Xero and QuickBooks. Use the ERP implementation timeline guide to plan scope, dependencies and your team’s involvement.
Do AI agents post to our ledger without anyone checking?
Only where your policy allows it, and never during migration. Agents connect, validate and map the data; your team reviews and approves before anything goes live. See how agentic accounting handles approvals and audit trails day to day once you’re live.
What happens to our historical data?
It moves with you. All Gravy brought six years of transaction history into Light, back to the company’s 2020 founding, with every year reconciled against trial balances before import. The ERP migration checklist covers which history to retain, how to reconcile it and what to approve before cutover.
Do we have to reissue our company cards?
No. Keep the cards you have, from Amex, your bank or a spend platform, and add them to Light as an external card account. Transactions come in by CSV or through the API, then get receipts, coding and posting like Light card spend. Cards from a spend platform stay on that provider’s plan. Moving to Light cards can wait, or not happen at all. Biofire, WorkflowMax and Ellidore already bring their existing cards into Light.
Does this work for a company like ours?
Customers who’ve moved to Light range from a gift-card infrastructure business trading in 23 currencies to a carbon-capture materials company scaling toward its first commercial plant. The common thread is more than one entity and a finance stack that stopped fitting, not a specific industry or size.
