How it works

1. Describe the split

A plan lists your environments, the targets, which legal entities go to which target, and the data projects to move, in order:

• Foundation and shared data (for example system setup, global address book, currencies) is moved once per target.
• Legal-entity setup (for example general ledger, payables and receivables setup) is moved for each legal entity to its target.
• Master data (for example customers and vendors) is an optional tier.
• Transactions stay out of scope; they are migrated separately.

Plans are edited in the web interface or kept as a file. The list of legal entities can be read straight from the source, and assignments can be uploaded from a spreadsheet.

2. Check before you run

FnOCarve validates the plan — every legal entity assigned exactly once, every target has an environment, no duplicate steps — and runs preflight checks against every environment: sign-in works, the app is registered, and every data project exists with the same name everywhere.

3. Run

Each data package is exported from the source and imported into the right target, in dependency order, with several legal entities in parallel per environment. Shared data always lands before legal-entity data.

If something fails, only the steps that depend on it are skipped; everything else continues. Fix the cause and retry failed — succeeded steps are never repeated. If a run is interrupted, start it again and it resumes.

4. Reconcile

After the imports, FnOCarve counts records per entity in source and target for each legal entity and produces a report with every difference highlighted.

Under the hood

• Microsoft's data management package REST API: export, import, status and error details, with automatic retry when F&O throttles requests.
• No secrets stored: only references to environment variables or Azure Key Vault secrets.