Ledger cutover
Stage your old system's trial balance and open items in the Finance migration workspace, tie them out, post them to the ledger, and sign the cutover off.
What ledger cutover does
Ledger cutover is the finance end of Data Migration. It takes the books you are leaving behind — chart of accounts, customers, vendors, a trial balance and your open invoices and bills — and brings them into Horizon Finance through a checked pipeline: stage, validate, tie out, post, sign off.
It comes with Finance: every organization that has Finance gets ledger cutover and Data Migration with it, and there is nothing separate to turn on. If an agent does any of this work for you, its runs are metered like any other agent run.
If you would rather do the conversion by hand — one journal entry and one document per open item — follow Bringing your existing books instead.
Who can do what
Accountants can start a migration, add data, validate it, propose corrections and import open items. Tying out, posting, signing off, approving corrections and closing a migration need an owner, admin or controller.
Start a migration
Open Data Migration under Setup & Configuration in the workspace navigation and follow the Finance
migration workspace card, or open /erp/finance/migration/workspace directly. Choose Start a migration and
pick the legal entity, the system you are coming from, and the conversion date — the first day you post in
Horizon. Each migration covers one legal entity; start another for each entity you are converting.
Add your data
The workspace lists what it collects, each with a CSV template to download:
- Chart of accounts, Customers, Vendors, Items, Tax codes and Dimensions;
- Trial balance timeline — the balances you are carrying over;
- Open AR invoices and Open AP bills.
Fill in each template and add the file against it. The panel tells you where to get each file for the system you chose. Tax codes and dimensions are staged and validated but not imported. A trial balance can be replaced by uploading it again.
Rows that fail validation are fixed with a correction, an edit to the staged row. A correction made by an owner, admin or controller applies straight away. It waits for a second person to approve it when the person who made it cannot approve corrections, as with accountants, or when your organization has turned on Migration correction approval in its finance settings. Validate the rows again after a correction.
Tie out and post
The readiness matrix shows the migration’s legal entity against three layers — GL Balances, Open Items and Positions — and the state each has reached. For the trial balance the order is fixed:
- Validate trial balance checks the staged rows, including that every staged period sums to zero. A run moves on only when no row is invalid.
- Tie out trial balance checks the account codes against your chart of accounts, the cutover month, the retained-earnings mapping and each account’s roll-forward. It needs the entity’s fiscal calendar and an active chart of accounts. The tie report lists any account failures, fiscal-year boundary closes and residual equity differences.
- Post opening balances posts the trial balance to the ledger, through a Migration Clearing suspense account.
Open items are validated and then imported as invoices and bills.
Sign off
When every run has finished, Sign off cutover freezes the migration. Only an owner, admin or controller can sign off, and their user must be linked to a finance employee. Sign-off refuses, and says why, if:
- a staged period does not tie, or nothing has been posted for the legal entity;
- corrections are still waiting for review;
- the Migration Clearing account does not net to zero, from this migration or from anything else on it.
If your organization turns on Migration sign-off segregation (Settings → Finance → Controls; owners and admins can change it), the person who uploaded the source data cannot also sign off. With it on, the uploader must be linked to a finance employee, or sign-off is refused.
Close a migration you are abandoning
Close migration ends a migration you will not finish. Owners, admins and controllers see it. It is refused once anything has been posted or open items have been imported; sign that migration off instead.