As a company grows, Mikro's capacity may start to fall short; in that case, a move to Odoo, Logo or SAP comes onto the agenda. But correctly moving the existing Mikro data is the hardest part of the transition. In this article we'll cover which data to move and how.
01. Main Data That Must Be Moved
Priority data sets:
- Account cards (customer, supplier)
- Stock cards and stock balances
- Chart of accounts and opening balances
- Accounting entries (last 2-3 years)
- Invoice and order history (last 1-2 years)
- Recipes (if there's production)
02. Data Extraction
Extracting data from Mikro is done two ways: standard Excel export (for small data) or a direct query via a SQL database connection (for large data). Direct SQL is the most flexible way but requires knowing Mikro's table structure.
03. Field Mapping
Mikro's field structure differs from the target system's field structure. For example, the account-code format in Mikro doesn't match partner_id in Odoo. A field-based transformation map (mapping) must be prepared.
04. Test Migration
Before going live, always do a trial migration in a test environment. At least 2-3 iterations should be run; each time, differences are found and corrected.
05. Parallel-Run Period
A 2-4 week parallel-run period is standard. After the new system goes live, Mikro also runs as a backup; month-end figures are compared. When zero difference holds for two weeks straight, the old system is shut down.