Preparing to move data from Mikro

Moving from Mikro should begin by deciding which records move and which system remains authoritative.

Define scope and ownership first

Record fields and ownership

Mikro export options may vary by product version, plan, and permissions. Check the official documentation and verify the records you need in a sample export.

• Inventory people, products, open work, and history separately.
• Identify record owners, permissions, and personal data in scope.
• Keep a read-only source backup and inspect a sample export.
• Confirm target field mapping, date/currency formats, and relationship keys in writing.
• Do not bulk-migrate before validating a small pilot by counts and sample records.

A controlled migration plan

Review Mikro’s official export documentation. An exportable record does not mean the destination imports the same fields, attachments, or relationships. Confirm MY OS-supported formats, record types, attachments, and rejected-row reporting in writing before migration.

Validation and rollback

• Compare source and destination counts by record type.
• Sample duplicates, missing required fields, and orphaned records.
• Have an authorized user verify financial/date fields; do not silently merge periods.
• Keep read-only access to the old system and a rollback plan until reconciliation is complete.

Frequently asked questions

Do not set a migration date before measuring volume, relationships, and validation scope.