---
title: "SYSPRO to Global Shop Solutions Migration | ClonePartner"
description: "SYSPRO to Global Shop Solutions: AR Invoices → Open AR invoices: Open items loaded; paid history archived. Engineer-led, zero downtime."
source: SYSPRO
target: Global Shop Solutions
canonical: "https://clonepartner.com/migrate/syspro-to-global-shop-solutions"
---

# SYSPRO → Global Shop Solutions migration

Engineer-led SYSPRO to Global Shop Solutions data migration. Move customers, suppliers, items and open orders out of SYSPRO into Global Shop Solutions, an ERP for manufacturers and job shops.

## Entity mappings

- **Customers** (SYSPRO) → **Customers** (Global Shop Solutions)
- **Suppliers** (SYSPRO) → **Suppliers** (Global Shop Solutions)
- **Inventory (Stock Items)** (SYSPRO) → **Parts** (Global Shop Solutions)
- **Bills of Materials** (SYSPRO) → **Bills of Materials** (Global Shop Solutions)
- **Sales Orders** (SYSPRO) → **Sales Orders** (Global Shop Solutions)
- **Purchase Orders** (SYSPRO) → **Purchase Orders** (Global Shop Solutions)
- **Work Orders** (SYSPRO) → **Work Orders** (Global Shop Solutions)
- **Lot Tracking** (SYSPRO) → **Lots and Serial Numbers** (Global Shop Solutions)
- **General Ledger Accounts** (SYSPRO) → **Chart of Accounts** (Global Shop Solutions)
- **GL Journal Entries** (SYSPRO) → **Opening balances** (Global Shop Solutions)
- **AR Invoices** (SYSPRO) → **Open AR invoices** (Global Shop Solutions)
- **AP Invoices** (SYSPRO) → **Open AP invoices** (Global Shop Solutions)
- **Customer Contacts** (SYSPRO) → **Customer contacts** (Global Shop Solutions)
- **Supplier Contacts** (SYSPRO) → **Supplier contacts** (Global Shop Solutions)

## 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 open Work Orders when moving from SYSPRO to Global Shop Solutions?

Work Orders are a workaround mapping: Global Shop Solutions cannot directly receive in-progress SYSPRO jobs, so the recommended approach is to close all open SYSPRO work orders before cutover and create the corresponding jobs fresh in Global Shop Solutions after the data migration completes. ClonePartner migrates the supporting data those jobs depend on — parts, bills of materials, customers — so the new jobs can be built against clean, migrated records. Posted history is usually loaded into Global Shop Solutions as opening balances or kept in an archive, rather than re-created as live transactions.

### Will my full AR and AP invoice history come across, or just the open items?

Only open AR and open AP invoices are loaded into Global Shop Solutions as live records; paid and closed invoice history is archived rather than migrated as active transactions. Posted history is usually loaded into Global Shop Solutions as opening balances or kept in an archive, rather than re-created as live transactions. If your team needs to look up paid invoices after cutover, export a structured archive before your SYSPRO licence expires, because SYSPRO's notice describes no read-only access after expiry.

### How does ClonePartner extract data from SYSPRO — do we need to give database access?

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.

### Do custom fields we built in SYSPRO carry over to Global Shop Solutions?

SYSPRO stores custom form fields in separate "plus tables" — for example, extra fields on the customer master live in [ArCustomer+] rather than [ArCustomer] — and these are not extracted automatically alongside the standard record. ClonePartner can extract and map those plus-table fields as part of scope, but the destination fields must already exist in Global Shop Solutions before the data loads, and Global Shop Solutions does not expose a public API reference, so the target fields typically need to be created manually in Global Shop Solutions first. Identify all plus-table fields you need to carry across during the scoping call so they can be included in the field mapping and validation plan.

### What do we need to set up in Global Shop Solutions before the migration can load data?

Several record types must exist in Global Shop Solutions before dependent data can be imported: the Chart of Accounts must be present before GL opening balances load, warehouses and tax codes must be configured before parts and orders can import, and supplier and customer records must land before their associated contacts, open invoices, or open orders. ClonePartner sequences the migration in dependency order — master data before transactional data — but records that have no equivalent in SYSPRO's exported dataset (such as warehouse locations you are adding as part of the move) must be created by your team in Global Shop Solutions ahead of the migration run. Confirm during scoping which setup records your Global Shop Solutions implementer will have ready, since a missing prerequisite record will block the dependent entities.

### How are GL journal entries handled — does our full transaction history move over?

General Ledger journal entry history is a workaround mapping: rather than replaying every individual posted transaction, history is typically loaded as opening balances and period net changes against the migrated Chart of Accounts. Posted history is usually loaded into Global Shop Solutions as opening balances or kept in an archive, rather than re-created as live transactions. Your finance team should agree on the opening balance date and confirm which prior periods, if any, need period net-change summaries loaded, and should export the detailed history to an archive before the SYSPRO licence expires.

## 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 → Global Shop Solutions migration.