ERP migration
Field-level mapping, validation, and rollback between MRPeasy and Acumatica. We move data and schema; workflows are rebuilt natively in Acumatica.
MRPeasy
Source
Acumatica
Destination
Compatibility
15 of 15
objects map 1:1 between MRPeasy and Acumatica.
Complexity
BStandard
Timeline
72–120 hours
Overview
MRPeasy structures its data across eight sections: CRM (customers, orders, invoices), Production Planning (manufacturing orders, BOMs, routings), Stock (items, inventory, lots), Procurement (purchase orders, vendors), and a built-in Accounting module. Custom fields attach to most objects through Settings → Custom Fields, supporting free text, dates, numbers, and pick-lists. Acumatica consolidates this into a unified platform using separate screens for each domain — AR301000 for customers, IN202000 for inventory items, AM201000 for production orders, AM205000 for bills of materials, and PM201000 for purchase orders — with an Organisation Structure screen handling company and branch setup. We map MRPeasy customers to Acumatica AR Customers (assigning a default BranchID for multi-location setups), stock items to Inventory Items (splitting per-warehouse quantity into Acumatica's warehouse-specific inventory records), manufacturing orders to Production Orders with operation-level mapping, and BOMs to Acumatica BOMs with revision tracking. Workflows, automations, approval chains, and MRPeasy's approval-system configuration do not migrate — we export those definitions as a structured rebuild reference for your Acumatica admin. Our migration engine uses MRPeasy's CSV export and REST API endpoints, targeting Acumatica's Import by Scenario and direct API endpoints, sequencing master data (items, customers, vendors) before transactional records to satisfy Acumatica's foreign-key requirements.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a MRPeasy object lands in Acumatica, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
MRPeasy
Customer
Acumatica
AR Customer (AR301000)
1:1MRPeasy customers map 1:1 to Acumatica AR Customers. Each customer requires a BranchID assignment — we use the MRPeasy site's primary branch or create a default branch. Customer addresses (billing and shipping) map to AR Contact and Address sub-tables; multiple shipping addresses per customer collapse to primary plus Contact records.
MRPeasy
Vendor
Acumatica
AP Vendor (AP303000)
1:1MRPeasy vendors map to Acumatica AP Vendors. The vendor's primary address and remittance address populate the Address and Payment By tabs. Currency and payment terms carry over where configured in MRPeasy; Acumatica's Terms field uses the AP Terms lookup (Net 30, FOB, etc.).
MRPeasy
Item (part/product)
Acumatica
Non-Stock Item / Stock Item (IN202000)
1:1MRPeasy items must be classified into Acumatica's item types: Stock Items (troublesome, manufactured), Non-Stock Items (purchased only), and Service Items. Whether an item is manufactured or purchased in MRPeasy determines the Item Type in Acumatica. Item's last purchase price maps to the Current Cost field; standard cost requires Acumatica-side valuation setup.
MRPeasy
Inventory Level (per site)
Acumatica
Inventory Receipt / Availability (IN402000)
1:1MRPeasy's per-site inventory quantity maps to Acumatica's warehouse-specific inventory rows. We generate IN Entry documents (IN303000) to set initial quantities per warehouse — one receipt line per item per MRPeasy site that maps to an Acumatica warehouse. On-hand cost derives from MRPeasy's cost-per-item field.
MRPeasy
Stock Lot
Acumatica
Lot/Serial Item Receipt (IN302000)
1:1MRPeasy lot numbers map to Acumatica Lot/Serial Nbr fields on IN302000 receipts. Lot attributes (expiry date, supplier lot) map to the Lot/Serial Details screen — MRPeasy's expiry date and custom lot fields become Lot Attributes in Acumatica. The lot number itself serves as the primary identifier, linking all attributes back to the original MRPeasy lot record for full traceability throughout the supply chain.
MRPeasy
BOM (Bill of Materials)
Acumatica
BOM & Recipe (AM205000)
1:1MRPeasy BOMs map to Acumatica BOMs (AM205000). MRPeasy supports flat BOM structures — multi-level BOMs (subassemblies with their own BOMs) decompose into a parent BOM revision referencing child BOMs as line items of type 'Phantom'. The BOM's active version becomes the 'Effective From' date in Acumatica.
MRPeasy
Routing (workstations and times)
Acumatica
Production Operation Routing (AM208000)
1:1MRPeasy operations attached to a manufacturing order map to Acumatica Production Operation Routing (AM208000). Workstations become Resources; operation times map to Machine Hours and Labor Hours per operation step. MRPeasy's workstation groups become Acumatica Work Centre Groups. Each operation sequence in MRPeasy generates a corresponding operation line in AM208000, maintaining the step-by-step routing structure that governs production flow.
MRPeasy
Manufacturing Order
Acumatica
Production Order (AM201000)
1:1Open MRPeasy manufacturing orders map to Acumatica Production Orders. The finished good, quantity, and scheduled dates transfer; materials are allocated from the BOM at migration time. MRPeasy's operation progress (% complete per operation) maps to Operation Detail rows in AM201000.
MRPeasy
Purchase Order
Acumatica
Purchase Order (PO301000)
1:1Open MRPeasy purchase orders map to Acumatica PO301000. Line items map by vendor part number or MRPeasy item code; quantities and unit costs transfer. Cancelled or completed MRPeasy POs are archived as reference records rather than imported as live documents.
MRPeasy
Customer Order (sales order)
Acumatica
Sales Order (SO301000)
1:1MRPeasy customer orders map to Acumatica Sales Orders (SO301000). Order dates, customer reference, line items, quantities, and unit prices transfer. MRPeasy order statuses (New, Confirmed, Invoiced) map to Acumatica status codes (On Hold, Open, Completed) — your admin defines the mapping rule before migration.
MRPeasy
Invoice
Acumatica
AR Invoice (AR301000) / AP Invoice (AP301000)
1:1MRPeasy invoices (customer-facing) map to Acumatica AR Invoices; purchase invoices map to AP Invoices. Original invoice dates and amounts transfer for audit continuity. MRPeasy's invoice-line tax codes map to Acumatica tax zones — your tax agency configuration must be active in Acumatica first.
MRPeasy
Custom Field (per object)
Acumatica
Extended Field (Customization → Customised Fields)
1:1MRPeasy custom fields migrate as Acumatica extended fields on the corresponding screen. Free-text, number, and date fields map directly. Pick-list custom fields require manual value setup in Acumatica's field detail editor — we provide a value-mapping table for your admin to configure before the import.
MRPeasy
User / Owner
Acumatica
Acumatica User (SM201010)
1:1MRPeasy users are matched to Acumatica users by email address. Users with no Acumatica account are flagged before migration; their records can be assigned to a fallback owner. MRPeasy role assignments (Admin, Manager, User) map to Acumatica roles but require manual Acumatica role-to-screen access configuration.
MRPeasy
Transfer Order
Acumatica
Inventory Transfer (IN303000)
1:1MRPeasy transfer orders (between sites) map to Acumatica Inventory Transfers. The sending warehouse and receiving warehouse map by site-to-branch name match. Completed transfers are imported as reference records; in-progress transfers are imported as open transfers for your team to receive in Acumatica.
MRPeasy
RMA (Customer Returns)
Acumatica
Sales Order (RMAs tab) / Returns Receipt (IN303000)
1:1MRPeasy RMAs map to Acumatica's RMA process: the return authorization becomes an open Sales Order with the RMA checkbox; receipt of returned items generates an IN303000 receipt. RMA dispositions (repair, replace, credit) map to Acumatica's Disposition codes — your admin configures these in IN Setup first.
| MRPeasy | Acumatica | Compatibility | |
|---|---|---|---|
| Customer | AR Customer (AR301000)1:1 | Fully supported | |
| Vendor | AP Vendor (AP303000)1:1 | Fully supported | |
| Item (part/product) | Non-Stock Item / Stock Item (IN202000)1:1 | Fully supported | |
| Inventory Level (per site) | Inventory Receipt / Availability (IN402000)1:1 | Fully supported | |
| Stock Lot | Lot/Serial Item Receipt (IN302000)1:1 | Fully supported | |
| BOM (Bill of Materials) | BOM & Recipe (AM205000)1:1 | Fully supported | |
| Routing (workstations and times) | Production Operation Routing (AM208000)1:1 | Fully supported | |
| Manufacturing Order | Production Order (AM201000)1:1 | Fully supported | |
| Purchase Order | Purchase Order (PO301000)1:1 | Fully supported | |
| Customer Order (sales order) | Sales Order (SO301000)1:1 | Fully supported | |
| Invoice | AR Invoice (AR301000) / AP Invoice (AP301000)1:1 | Fully supported | |
| Custom Field (per object) | Extended Field (Customization → Customised Fields)1:1 | Fully supported | |
| User / Owner | Acumatica User (SM201010)1:1 | Fully supported | |
| Transfer Order | Inventory Transfer (IN303000)1:1 | Fully supported | |
| RMA (Customer Returns) | Sales Order (RMAs tab) / Returns Receipt (IN303000)1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
MRPeasy gotchas
API access locked behind Unlimited plan
3000-line CSV import cap per upload
Workstations and Storage Locations must be manually configured
Active Manufacturing Orders trigger dynamic rescheduling on import
Transfer Order 'Received' status is manual
Acumatica gotchas
API user licenses cap concurrent sessions and request throughput
Multi-tenant filtering requires CompanyID awareness
Custom fields require separate discovery before field mapping
Notes and attachments use a separate linked table structure
Implementation timelines frequently run 3–9 months end-to-end
Pair-specific challenges
Migration approach
Schema discovery and Acumatica environment audit
FlitStack AI reads MRPeasy's object inventory via API and CSV export — scanning all sections (CRM, Stock, Production, Procurement, Settings) to count unique item types, BOM structures, open order volumes, and custom field definitions. We simultaneously audit the target Acumatica tenant: identifying active screens, configured branches and warehouses, existing inventory items, and tax zone setup. This produces a Schema Gap Report identifying any Acumatica branches or lot attribute configurations that must be created before data lands, plus a custom field creation checklist for your admin.
Sequence master data and resolve foreign keys
Acumatica enforces referential integrity — inventory items must exist before BOMs, customers before sales orders, vendors before purchase orders. We sequence the migration in dependency order: first Vendors and Customers (no dependencies), then Inventory Items, then Warehouses and Branches, then BOMs and Routings, then Purchase Orders and Sales Orders, then Manufacturing Orders. For each record we attempt to resolve owner and branch assignments by email match (users) and site-to-branch name match (warehouses). Any record with an unresolved dependency is flagged in a Pre-Migration Exception Report for your team to resolve before the run.
Run sample migration with field-level diff
A representative slice — typically 200–500 records across customers, items, a BOM with 10+ lines, an open manufacturing order, and an open PO — migrates first into a staging Acumatica company. We generate a field-level diff comparing source values against destination field values, with highlighted discrepancies for pick-list mappings, branch assignments, and date fields. This validation step catches BOM revision mapping issues, lot attribute configuration gaps, and custom field value mismatches before the full run commits. Your team reviews the diff and approves the mapping rules before we proceed.
Execute full migration with delta-pickup window
The full migration runs master data first, then transactional records. A delta-pickup window — typically 24–48 hours after the initial run — captures any new or modified records created in MRPeasy during the cutover period. All operations are logged in an audit trail (source record ID, destination record ID, operation type, timestamp, user). If reconciliation fails — for example, if BOM line counts or inventory quantities don't match — one-click rollback reverts the Acumatica tenant to its pre-migration snapshot so your team can investigate without data loss.
Post-migration reconciliation and workflow rebuild handover
After the delta-pickup closes, we run a reconciliation report comparing record counts, inventory quantities, and open order totals between MRPeasy's final state and Acumatica. Discrepancies are investigated and corrected. We then deliver the exported workflow definitions (approval rules, automation triggers, MRPeasy sequences) as structured configuration documents your Acumatica admin can use to rebuild them in the generic Approval Workflow engine (EP205020) and Acumatica's Automation Schedules screen.
Platform deep dives
MRPeasy
Source
Strengths
Weaknesses
Acumatica
Destination
Strengths
Weaknesses
Complexity grading
Standard ERP migration. 2 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across MRPeasy and Acumatica.
Object compatibility
2 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
MRPeasy: Not publicly documented.
Data volume sensitivity
MRPeasy doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during MRPeasy to Acumatica migration scoping. Not seeing yours? Book a call.
Walk through your MRPeasy to Acumatica migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave MRPeasy
Other ways to arrive at Acumatica
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.