--- title: "SYSPRO to SOS Inventory Migration | ClonePartner" description: "SYSPRO to SOS Inventory: Bills of Materials → Item BOM: SOS documents its BOM endpoint as beta. Engineer-led, zero downtime." source: SYSPRO target: SOS Inventory canonical: "https://clonepartner.com/migrate/syspro-to-sos-inventory" --- # SYSPRO → SOS Inventory migration Engineer-led SYSPRO to SOS Inventory data migration. Move customers, suppliers, items and open orders out of SYSPRO into SOS Inventory, which runs inventory and orders alongside QuickBooks Online. ## Entity mappings - **Customers** (SYSPRO) → **Customers** (SOS Inventory) - **Suppliers** (SYSPRO) → **Vendors** (SOS Inventory) - **Inventory (Stock Items)** (SYSPRO) → **Items** (SOS Inventory) - **Bills of Materials** (SYSPRO) → **Item BOM** (SOS Inventory) - **Sales Orders** (SYSPRO) → **Sales Orders** (SOS Inventory) - **Purchase Orders** (SYSPRO) → **Purchase Orders** (SOS Inventory) - **GRN (Goods Received Notes)** (SYSPRO) → **Item receipts** (SOS Inventory) - **Work Orders** (SYSPRO) → **Work Orders** (SOS Inventory) - **Inventory Adjustments** (SYSPRO) → **Adjustments** (SOS Inventory) - **Lot Tracking** (SYSPRO) → **Lots and serial numbers** (SOS Inventory) - **AR Invoices** (SYSPRO) → **Invoices** (SOS Inventory) - **General Ledger Accounts** (SYSPRO) → **Not available** (SOS Inventory) - **GL Journal Entries** (SYSPRO) → **Not available** (SOS Inventory) ## 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 General Ledger accounts and journal entries when I move from SYSPRO to SOS Inventory? SOS Inventory does not hold a general ledger; GL accounts and posted journal entries live in the QuickBooks Online file that SOS connects to, not in SOS itself. ClonePartner cannot migrate GL data into SOS Inventory because the target endpoint does not exist. Before cutover, your team needs to confirm that the corresponding chart of accounts is already set up in the linked QuickBooks Online company, and any historical journal entries must be handled directly in QuickBooks outside of this migration. ### Can my Bills of Materials from SYSPRO be migrated into SOS Inventory? SOS Inventory's BOM endpoint is documented by the vendor as beta, so ClonePartner uses a workaround path rather than a direct API write. Migration proceeds, but you should run a post-migration review of each transferred BOM in SOS Inventory to confirm component quantities, units of measure and multi-level structures resolved correctly, since beta endpoints can behave inconsistently across SOS account configurations. Any BOM that fails the workaround is flagged in the validation report for manual re-entry. ### Does SYSPRO's version or deployment type affect what can be extracted for the migration? 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 fields come across to SOS Inventory? SYSPRO stores custom form fields in separate plus tables named after the primary table with a plus suffix, for example ArCustomer+ for customer custom fields. ClonePartner extracts these tables explicitly and maps them to available SOS Inventory custom fields, but SOS Inventory has its own fixed set of custom field types per object, so not every SYSPRO custom field has a direct landing spot. Fields that cannot be mapped to a supported SOS custom field are documented in the migration report, and your team will need to decide whether to create matching custom fields in SOS Inventory before the migration run or accept that those values will not transfer. ### My SYSPRO data spans multiple companies — does ClonePartner handle that? Each SYSPRO company has its own SQL Server database, so multi-company extractions run company by company rather than as a single pull. ClonePartner supports this, but each company-to-SOS mapping needs to be scoped individually, including how customers, inventory items or suppliers that appear in more than one SYSPRO company should be deduplicated or merged in SOS Inventory. Clarify during the scoping call whether the target is a single SOS Inventory account or separate accounts per company, as that changes the mapping design significantly. ### Are Work Orders and lot tracking data available in SOS Inventory after migration, or do those require a specific plan? Work Orders and lot or serial number tracking both have direct mappings from SYSPRO to SOS Inventory, but SOS Inventory's Work Order and job objects are only available on the Pro plan. If your SOS account is on a lower tier, those records cannot be written via the API and will appear as failures in the validation report. Confirm your SOS Inventory subscription level before the migration run so that plan-gated objects are not excluded unexpectedly. ## 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 → SOS Inventory migration.