Migrate your MRPeasy data

Items are the core stock record in MRPeasy, holding part numbers, descriptions, costs, and stock quantities. CSV import creates new items or updates existing ones by part number match. Inventory quantity and cost can be set on initial creation import only; subsequent stock level updates require a dedicated inventory import. We preserve all item properties and map them 1:1 into the destination.

BOMs define the component structure for manufactured items. MRPeasy supports multi-level BOMs, co-product BOMs, and disassembly BOMs (Professional+). We map the parent-item relationship and all component lines, preserving quantity-per and scrap rates. Co-product and disassembly variants are flagged for explicit mapping against the destination's BOM model.

Routings define the production operations sequence, workstations, and labor times for manufactured items. MRPeasy supports overlap, parallel execution, and piece-payment operations. We transfer routing steps in sequence order, preserving workstation assignments and duration estimates. Any custom operation types are noted for manual review post-migration.

Manufacturing Orders are the production tickets linking BOM and Routing to actual production. Historical MO records are migrated as read-only history. Active/open MOs require rescheduling logic since MRPeasy's dynamic rescheduling engine may recalculate dates on import. We flag the MO status field explicitly to prevent accidental re-triggering of scheduling.

Customers live in the CRM section and support CSV import by matching on customer code or name. Import handles basic fields (name, contact, address, tax ID) and can update existing records. We map Customer records to the destination CRM, preserving any Customer Status customizations.

Vendors are imported before Items in MRPeasy's documented sequence because Items reference vendor purchase terms. We follow that dependency order during migration. Purchase Terms per vendor-item pair can be imported in a separate step after item creation.

Current stock quantities and costs per storage location are imported via a dedicated inventory import at Stock -> Inventory -> Import from CSV. The file limit is 3000 lines per upload; we chunk large inventories accordingly. Where multi-site and multi-location storage is used, we map site and location codes explicitly to avoid quantity misplacement.

Stock Lots track batch traceability with received status on creation. MRPeasy imports lot records via CSV with fields for part number, lot/batch number, quantity, expiry date, and storage location. New lots always land with 'Received' status. We preserve lot metadata (expiry, batch number, supplier traceability) through the transfer.

Custom fields can be added to the MRPeasy database via Settings -> System -> Custom fields. They are available on Professional and above. During migration, any custom field definitions must be replicated in the destination first; we then map the values as custom properties on the corresponding object. Field types and picklist values are cross-referenced manually.

Price Lists define customer-specific or product-specific pricing. They are imported separately from Customers and Items. We map price list lines to the destination's pricing object, preserving currency, price break tiers, and effective dates.

Transfer Orders move stock between sites and storage locations. They have a defined lifecycle (New, Ready, Shipped, Received, Canceled) and can include transportation costs and waybill documentation. We migrate Transfer Order headers and line items, but note that the 'Received' status must be assigned manually post-migration per MRPeasy's design.

Workstations and Workstation Groups cannot be set up via CSV import — they must be configured manually in MRPeasy's Settings. We flag these as requiring manual setup in the destination before Manufacturing Orders can be scheduled against them.

MRPeasy includes a standard accounting module. We map the Chart of Accounts to the destination's accounting structure, flagging any non-standard account codes or custom account types for manual reconciliation. Open AP/AR balances are migrated as opening balances rather than live transactions.

MRPeasy manages users and roles in Settings -> User management. User records are exported via the platform's table export function. We map active users to the destination system, preserving role assignments. Note that MRPeasy bills per user, so we flag the user count against the destination's licensing model.