--- title: "SYSPRO to Plex Migration | ClonePartner" description: "SYSPRO to Plex: Work Orders → Work Orders: Close open SYSPRO jobs before cutover and start new jobs in Plex. Engineer-led, zero downtime." source: SYSPRO target: Plex canonical: "https://clonepartner.com/migrate/syspro-to-plex" --- # SYSPRO → Plex migration Engineer-led SYSPRO to Plex data migration. Move customers, suppliers, items and open orders out of SYSPRO into Plex, a cloud manufacturing platform with built-in MES. ## Entity mappings - **Customers** (SYSPRO) → **Customers** (Plex) - **Suppliers** (SYSPRO) → **Suppliers** (Plex) - **Inventory (Stock Items)** (SYSPRO) → **Parts** (Plex) - **Bills of Materials** (SYSPRO) → **Bills of Materials** (Plex) - **Sales Orders** (SYSPRO) → **Sales Orders** (Plex) - **Purchase Orders** (SYSPRO) → **Purchase Orders** (Plex) - **Work Orders** (SYSPRO) → **Work Orders** (Plex) - **Lot Tracking** (SYSPRO) → **Lots and Serial Numbers** (Plex) - **General Ledger Accounts** (SYSPRO) → **Chart of Accounts** (Plex) - **GL Journal Entries** (SYSPRO) → **Opening balances** (Plex) - **AR Invoices** (SYSPRO) → **Open AR invoices** (Plex) - **AP Invoices** (SYSPRO) → **Open AP invoices** (Plex) - **Customer Contacts** (SYSPRO) → **Customer contacts** (Plex) - **Supplier Contacts** (SYSPRO) → **Supplier contacts** (Plex) ## 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 ### What happens to my SYSPRO work orders during the migration? Work orders are a workaround mapping: Plex has no direct equivalent import path for in-flight SYSPRO jobs. Before cutover, your team needs to close all open SYSPRO work orders and then create the corresponding new jobs directly in Plex. ClonePartner migrates the data that can be moved, but the close-and-recreate step for work orders is a task your operations team must complete as part of your Plex go-live, not something our migration tooling handles. ### Does my full invoice history come across, or just what's still open? Only open AR and AP invoices are loaded into Plex; paid and closed invoice history is archived rather than imported as live records. Posted history is usually loaded into Plex as opening balances or kept in an archive, rather than re-created as live transactions. Before migration, you should export and store any paid invoice history you need for audit or reference purposes, and confirm with your accounting team which period-net-change figures need to come across as GL opening balances. ### How does ClonePartner actually read data out of SYSPRO? 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 SYSPRO custom form fields migrate to Plex? SYSPRO stores custom form fields in separate 'plus tables' — for example, extra customer fields live in [ArCustomer+] rather than the main customer table — so they require a separate extraction and explicit mapping step. We extract those fields and map them to the closest available Plex target fields, but Plex may not have a native home for every custom field your team has added in SYSPRO. Any fields that have no Plex equivalent will need to be reconfigured as custom attributes in Plex by your implementation team; ClonePartner identifies them during scoping so nothing is discovered silently at cutover. ### What do we need to set up in Plex before the migration data can load? Plex requires certain prerequisite records to exist before dependent data can be imported: GL accounts must be in place before journal opening balances load, warehouses and tax codes must exist before inventory and order records can reference them, and so on. If those records are missing, the import will reject the dependent rows rather than create them on the fly. We provide a pre-migration checklist of the reference data that must be configured in Plex first, which your Plex implementation team should complete before we begin the production load. ### Does migrating one SYSPRO company mean all our companies come across automatically? No. Each SYSPRO company has its own isolated SQL Server database, so multi-company extractions run company by company rather than as a single pull. If you operate multiple SYSPRO companies, each one is scoped and priced as a distinct source, and the entity mappings and custom-field structures may differ between companies. Make sure you identify all active company databases during the scoping call so the full scope is captured in your fixed project price. ## 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 → Plex migration.