Migration & data

Bring existing business history into Omnizone without rewriting how you already work.

Book a demo · See all modules

What you get

Who runs this

Questions

Can one source company feed two workspaces? No — one source company binds to one workspace.

The binding prevents the same source company from being imported into a second workspace, and prevents a second source company from overwriting an already-bound workspace.

What about lighter migrations? Spreadsheet import under Settings → Data covers lighter moves.

When a full company import is not required, spreadsheet import moves selected masters and documents without the full source-system binding flow.

What history can a full import bring? Customers, vendors, employees, CoA, invoices, credits, ledgers, and currencies.

Full company import is designed for real operating history — not a demo subset — so the workspace opens with books you can close.

Does import rewrite how we already work? No — the goal is to bring history without inventing a new operating model.

Chart codes, document numbers, and party masters keep their source identity where the product supports it, so teams recognise Friday’s work on Monday.

Can we export after we are live? Yes — permission-gated export kinds and structured org backup.

Backup and partial CSV exports stay behind the same role gates as the rest of the workspace so sensitive ledgers are not a free download.

Will import delete production history to clean up? No — destructive clean-ups are not part of the migration promise.

Omnizone does not delete production history to make an import look tidy. Corrections use the ordinary posting and void paths after you are live.

What this does not do

Connected to the rest of the system

FAQ

What about lighter migrations?

Spreadsheet import under Settings → Data covers lighter moves when a full company import is not required.