--- title: "SYSPRO to QAD Migration | ClonePartner" description: "SYSPRO to QAD: Work Orders → Work Orders: Close open SYSPRO jobs before cutover and start new jobs in QAD. Engineer-led, zero downtime." source: SYSPRO target: QAD canonical: "https://clonepartner.com/migrate/syspro-to-qad" --- # SYSPRO → QAD migration Engineer-led SYSPRO to QAD data migration. Move customers, suppliers, items and open orders out of SYSPRO into QAD Adaptive ERP, built for manufacturers. ## Entity mappings - **Customers** (SYSPRO) → **Customers** (QAD) - **Suppliers** (SYSPRO) → **Suppliers** (QAD) - **Inventory (Stock Items)** (SYSPRO) → **Parts** (QAD) - **Bills of Materials** (SYSPRO) → **Bills of Materials** (QAD) - **Sales Orders** (SYSPRO) → **Sales Orders** (QAD) - **Purchase Orders** (SYSPRO) → **Purchase Orders** (QAD) - **Work Orders** (SYSPRO) → **Work Orders** (QAD) - **Lot Tracking** (SYSPRO) → **Lots and Serial Numbers** (QAD) - **General Ledger Accounts** (SYSPRO) → **Chart of Accounts** (QAD) - **GL Journal Entries** (SYSPRO) → **Opening balances** (QAD) - **AR Invoices** (SYSPRO) → **Open AR invoices** (QAD) - **AP Invoices** (SYSPRO) → **Open AP invoices** (QAD) - **Customer Contacts** (SYSPRO) → **Customer contacts** (QAD) - **Supplier Contacts** (SYSPRO) → **Supplier contacts** (QAD) ## 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 migration? Work Orders require a workaround: open SYSPRO jobs must be closed before cutover, and equivalent jobs are then created fresh in QAD rather than migrated directly. Any in-progress job costs, routing steps, or partial completions recorded in SYSPRO will not carry over as live transactional detail, so your team should document current job status and quantities before the cutover window. ClonePartner will coordinate the timing of this step with you during scoping. ### Will paid AP and AR invoice history come across from SYSPRO to QAD? Only open (unpaid) AR and AP invoices are loaded into QAD; Posted history is usually loaded into QAD as opening balances or kept in an archive, rather than re-created as live transactions. General Ledger history follows the same pattern: prior-period entries are brought across as opening balances and period net changes rather than as individual journal entries. If your team needs access to paid invoice detail after cutover, export the history to an archive or reporting database before your SYSPRO licence expires, because SYSPRO's notice describes no read-only access after expiry. ### Do custom fields I've added in SYSPRO migrate to QAD? SYSPRO stores custom form fields in separate plus tables named with a '+' suffix — for example, ArCustomer+ for customer extensions — which sit outside the standard business object schemas and require a separate extraction step. ClonePartner maps these fields during scoping and identifies which have a corresponding field in QAD and which need to be created or configured in QAD by your implementation team before the data load runs. Unmapped custom fields that have no QAD equivalent will not transfer automatically; those values must be handled either through QAD configuration or accepted as out of scope. ### What needs to be set up in QAD before ClonePartner can load the data? Several SYSPRO business objects require prerequisite records to exist in the target before dependent data can import: GL accounts must be present before journal entries or opening balances load, and warehouses and tax codes must be configured before inventory and order records are accepted. Because QAD documents its business APIs inside each customer instance rather than via a public endpoint, your QAD administrator will also need to provide ClonePartner with API access credentials and confirm which endpoints are active in your specific instance. ClonePartner will produce a prerequisites checklist during the scoping call so your team knows exactly what to configure before migration begins. ### Does it matter which version of SYSPRO or QAD we're running? On the SYSPRO side, we usually read the SQL Server company database directly, so the SYSPRO 8 release matters less than the deployment: on Syspro Cloud ERP, SYSPRO's read-only OData service is the only access route. On the QAD side, the REST API and its JSON support differ between QAD Enterprise Edition and QAD Cloud, and not every endpoint supports JSON, so the API surface ClonePartner calls against is confirmed against your specific instance before migration begins. ### What about multi-company SYSPRO setups — can all entities migrate at once? SYSPRO gives each company its own SQL Server database, so multi-company extractions must run company by company rather than in a single pass. ClonePartner scopes each company as a discrete extraction unit, maps it to the corresponding QAD domain or entity, and sequences the loads to respect cross-company dependencies such as shared GL accounts or intercompany supplier records. The project price covers the full scope agreed at kickoff, so the number of companies should be confirmed during the scoping call to ensure it is included. ## 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 → QAD migration.