We don’t ask you to trust a new ledger.

Why this exists

Replacing a general ledger is the highest-consequence software decision a mid-market company makes. The books are the record used to file taxes, satisfy an audit, service debt covenants, and value the business. A migration that quietly loses fidelity does not produce an outage — it produces wrong numbers that nobody notices until a year-end review, which is far worse.

Every ERP vendor knows this, and the industry’s answer has been to manage the fear with process: a long implementation, a parallel-run month, a cutover weekend, a consultant on site. That is expensive, it is slow, and it still asks you to take the final step on faith.

The shadow ledger replaces faith with evidence. Instead of a two-week parallel run at the end of a nine-month project, you get a parallel run that begins in week one and never stops. By the time switching is on the table, you are not evaluating a promise. You are looking at a year of your own closed periods, agreeing.

What cutover actually looks like

Because the ledger has been running the whole time, going live is not a migration event. It is a change in which system is authoritative.

1. Confirm the streak. Three or more consecutive closed months tied at zero variance. We will not sell you a cutover before this — it is a gate, not a guideline.
2. Freeze the source. Your existing system goes read-only at period end. No dual entry, no overlap window.
3. Turn off the write-back. erp.io stops mirroring and starts recording. The chart of accounts, sub-ledgers, open items, and history are already in place.
4. Close the first period natively. With the prior period’s tie-out sitting next to it as the control.

What the tie-out proves

The reconciliation is not a summary comparison. It ties at four levels, and a failure at any level is reported rather than smoothed over.

• Trial balance — total debits and credits agree, and net to zero.
• Account level — every account balance matches, per period.
• Sub-ledger to control — AR and AP detail tie to their control accounts.
• Transaction level — any variance resolves to the specific source transaction that caused it, with a reason.

Variances are normal early on. Timing differences, unmapped accounts, and classification disagreements surface in the first fortnight and get resolved — which is itself the point. Those are the same problems that would have detonated during a traditional cutover weekend, found months earlier, with nothing at stake.