etaill.com
MIGRATION

Move to etaill without losing the history that makes your accounts useful.

The migration workflow is designed around controlled import, mapping, duplicate detection and review rather than a one-click black box.

Before the business relies on the migrated books, etaill keeps import totals, duplicate counts and unresolved rows visible so the owner or accountant can compare the result with the source system and investigate anything that does not reconcile cleanly.

1

Connect or export

Start from Xero, QuickBooks, FreeAgent or a structured CSV export.

2

Import records

Bring supported contacts, invoices, bills, transactions and opening information into a migration run.

3

Map and deduplicate

Identify duplicates and map source data into etaill's accounting structure.

4

Review issues

Keep unsupported or uncertain rows visible instead of silently dropping them.

5

Approve the move

Accountant review can sign off a clean migration before the business relies on it.

What migration protects against

Duplicate transactions, missing references, unsupported rows, opening-balance inconsistencies and loss of review context are all reasons to use a controlled migration process.

etaill stores migration counts and issues so owners and accountants can see what happened.

INTEGRATIONS

Migration and live sync are different things.

A migration can work from exports even when a live provider OAuth connection is not yet configured.

See provider readiness →