--- title: "SYSPRO to MRPeasy Migration | ClonePartner" description: "SYSPRO to MRPeasy: Suppliers → Vendors: Vendors are read-only in the MRPeasy API; load by import. Engineer-led, zero downtime." source: SYSPRO target: MRPeasy canonical: "https://clonepartner.com/migrate/syspro-to-mrpeasy" --- # SYSPRO → MRPeasy migration Engineer-led SYSPRO to MRPeasy data migration. Move customers, suppliers, items and open orders out of SYSPRO into MRPeasy, manufacturing software for small manufacturers. ## Entity mappings - **Customers** (SYSPRO) → **Customers** (MRPeasy) - **Suppliers** (SYSPRO) → **Vendors** (MRPeasy) - **Inventory (Stock Items)** (SYSPRO) → **Stock Items** (MRPeasy) - **Bills of Materials** (SYSPRO) → **BOMs** (MRPeasy) - **Sales Orders** (SYSPRO) → **Customer Orders** (MRPeasy) - **Purchase Orders** (SYSPRO) → **Purchase Orders** (MRPeasy) - **Work Orders** (SYSPRO) → **Manufacturing Orders** (MRPeasy) - **Lot Tracking** (SYSPRO) → **Lots and serial numbers** (MRPeasy) - **AR Invoices** (SYSPRO) → **Invoices** (MRPeasy) - **AP Invoices** (SYSPRO) → **Supplier invoices** (MRPeasy) - **General Ledger Accounts** (SYSPRO) → **Accounts** (MRPeasy) ## What we migrate ### Data Types - **Chart of Accounts** — GL account structure, segments, and hierarchies - **General Ledger Entries** — Journal entries, transactions, and balances - **Accounts Payable** — Vendor records, bills, and payment history - **Accounts Receivable** — Customer records, invoices, and payment history - **Inventory & Items** — Product records, stock levels, and warehouses - **Purchase Orders** — PO records with line items and vendor links - **Sales Orders** — SO records with line items and customer links ### Migration Filter - **Date Range Filter** — Migrate records from a specific time period - **Entity Selection** — Select specific subsidiaries or business units - **Module Filter** — Choose which ERP modules to migrate ## Frequently asked questions ### Why can't my suppliers just be migrated directly, and what do I need to do instead? The MRPeasy API marks Vendors as read-only, so ClonePartner cannot write supplier records through the API the way it can with customers or stock items. Instead, vendors are loaded via MRPeasy's bulk import mechanism, which means your MRPeasy environment must be on the Unlimited plan before migration starts and the import files must be staged and reviewed before cutover. You should verify all vendor records in MRPeasy after the import step before decommissioning SYSPRO as your source of truth. ### What happens to open SYSPRO work orders when we migrate to MRPeasy? Open SYSPRO jobs (Work Orders) do not have a clean direct write path into MRPeasy Manufacturing Orders, so ClonePartner's process requires that all open jobs be closed or finalised in SYSPRO before cutover. Any job left open at migration time will not land in MRPeasy as an active Manufacturing Order; it needs to be recreated manually in MRPeasy by your team. Plan a freeze window before cutover specifically to close in-progress production jobs in SYSPRO. ### Does my SYSPRO setup need anything special before ClonePartner can extract data from it? We usually read SYSPRO directly from its SQL Server company database. That reaches every table, including the custom form plus tables such as [ArCustomer+]. Where direct SQL access is not possible, we use SYSPRO's read-only OData service, which SYSPRO describes as the only access mechanism in its Syspro Cloud ERP environment. Each SYSPRO company has its own database, so multi-company sites are extracted company by company, and we confirm the access route on the scoping call. ### Will my SYSPRO custom form field data come across to MRPeasy? SYSPRO stores custom form fields in separate 'plus tables' (for example [ArCustomer+] for customer custom fields), which are not returned by standard business object queries and require an explicit additional extraction step. ClonePartner handles this extraction, but those fields must be mapped to an equivalent MRPeasy field or note field before migration; any custom field with no MRPeasy equivalent cannot be stored as a native field and will be flagged during scoping. Review your custom form fields in SYSPRO ahead of the scoping call so you can decide which ones need to land in MRPeasy and in what form. ### Do I need to be on a specific MRPeasy plan for the migration to work? Yes. MRPeasy's API is available only on the Unlimited pricing plan, and MRPeasy support does not assist with API development or troubleshoot API access issues. ClonePartner uses REST v2 for objects that support write operations and falls back to v1 where REST v2 is still read-only, but either way the Unlimited plan must be active in your MRPeasy account before migration can begin. Confirm your plan tier during the scoping call so there are no delays at the start of the migration window. ### What MRPeasy configuration has to be done by hand after the data lands? MRPeasy requires certain prerequisite configuration — warehouses, tax codes, and GL account structures — to exist before dependent records such as inventory and invoices can be imported successfully; ClonePartner flags these during validation, but your team must create or confirm them in MRPeasy before the final load runs. Workflow rules, user permissions, notification settings, and any production routing logic tied to Manufacturing Orders are platform configuration, not data, so they are not moved by the migration and must be set up by your team in MRPeasy. Posted history is usually loaded into MRPeasy as opening balances or kept in an archive, rather than re-created as live transactions. ## Get a fixed-price quote [Talk to an engineer](https://clonepartner.com/talk-to-us?duration=30&utm_source=xtoy&utm_medium=button&utm_campaign=demo_bookings&utm_content=cta_click&utm_term=demo_button_click) about your SYSPRO → MRPeasy migration.