Move to Plain Accounts | Accounting migration

The workflow, start to finish

1. Choose the conversion date and retained history
2. Clean and export the source data
3. Map contacts, accounts, tax and tracking
4. Import in dependency order
5. Reconcile control totals and approve handover

Every stage has a visible status. People can see what is ready, what is waiting and what needs correction instead of relying on a private spreadsheet or an email thread.

Information that carries forward

Source identifiers and migration batches allow retries without creating uncontrolled duplicates. Errors remain tied to the row and import stage that produced them.

That continuity reduces duplicate entry and also makes correction safer: the team can follow the result back through its posting, approval and source instead of changing an unexplained total.

Controls and exceptions

Preview, validation, idempotent retries, opening-balance checks and tenant-scoped processing protect the target workspace.

Plain separates drafting from privileged actions. An exception remains reviewable, with a useful explanation, rather than being silently forced through merely to complete a workflow.

A realistic example

A Xero migration imports the chart and active contacts first, then open invoices and bills, bank opening balances and supporting payroll totals before comparing receivables, payables and trial balance to the source.

The live demo uses sample business data and simulated external actions so visitors can test the internal workflow without sending a message, moving money, connecting a bank or lodging with an authority.

Connected to the rest of Plain

CleaningCentral records are filtered to active clients with non-draft invoices before accounting activation; linked invoices and payments keep their operational source identifiers.

Once authorised activity posts to the ledger, the same result is available to account activity, financial statements, budgets, audit history and month-end review according to the user’s role.

What to confirm before relying on it

Do not cancel the old system until control totals, document samples, user access, exports and the agreed handover checklist pass. Regulated filing history may require separate retention.

During setup, confirm the workspace country, accounting basis, tax treatment, financial year, account mappings, approval rules and user access. Plain provides the controlled workflow; the customer remains responsible for its business decisions and professional advice.