Data migration

Goal

Import master and historical data from external accounting systems with a safe preview (dry-run) before commit. Failed commits roll back the whole batch.

Who it is for

Operators with migration.import only (powerful — treat as break-glass).

Preconditions

• Target tenant is the one you intend to load.
• Source files / staged snapshots ready:
  • Manager.io — .manager upload
  • Shamel Lite / ShamelPro — supported entity packs
  • Hesabate — staged server snapshot
• Prefer a backup before large commits on lasting environments.

Steps

1. Open Administration → Organization → Data Migration.
2. Choose source system.
3. Configure connection / upload; use Test connection when offered.
4. Select entity scope (accounts, parties, items, journals, invoices, … — set varies by source).
5. Run Preview (dry-run). Review counts and row-level issues in the report.
6. Import (commit) only when preview looks correct. Use Stop only while status is queued/processing.
7. Open history / report panels for prior runs and drill into failed rows.

Result

Committed entities appear in BlueMatrix masters and documents per the importer. Preview alone writes nothing.

Hard stops

Symptom	Cause	What to do
Only queued/processing can be cancelled	Import already finished/failed	Start a new run if needed
Unknown migration entity	Entity key not in source pack	Remove from scope
Connection / upload 422	Bad file or credentials	Fix upload/path/credentials
Empty failed batch 422	Nothing to commit after errors	Fix preview errors first
Confirm copy: failed import rolls back	Transactional safety	Re-preview after fixes

Related

• Industry packs
• Tenant settings