---
title: "SYSPRO to Xero Migration | ClonePartner"
description: "SYSPRO to Xero: Inventory (Stock Items) → Items: Xero items carry no warehouse or lot detail. Engineer-led, zero downtime."
source: SYSPRO
target: Xero
canonical: "https://clonepartner.com/migrate/syspro-to-xero"
---

# SYSPRO → Xero migration

Engineer-led SYSPRO to Xero data migration. Move customers, suppliers, invoices and ledger balances out of SYSPRO into Xero.

## Entity mappings

- **Customers** (SYSPRO) → **Contacts** (Xero)
- **Suppliers** (SYSPRO) → **Contacts** (Xero)
- **AR Invoices** (SYSPRO) → **Invoices (ACCREC)** (Xero)
- **AP Invoices** (SYSPRO) → **Invoices (ACCPAY)** (Xero)
- **General Ledger Accounts** (SYSPRO) → **Accounts** (Xero)
- **GL Journal Entries** (SYSPRO) → **Manual Journals** (Xero)
- **Inventory (Stock Items)** (SYSPRO) → **Items** (Xero)
- **Purchase Orders** (SYSPRO) → **Purchase Orders** (Xero)
- **Quotations** (SYSPRO) → **Quotes** (Xero)
- **Currency Rates** (SYSPRO) → **Currencies** (Xero)
- **Tax Codes** (SYSPRO) → **Tax Rates** (Xero)
- **Cash Book Entries** (SYSPRO) → **Bank Transactions** (Xero)
- **Sales Orders** (SYSPRO) → **Not available** (Xero)
- **Bills of Materials** (SYSPRO) → **Not available** (Xero)
- **Work Orders** (SYSPRO) → **Not available** (Xero)

## 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 Sales Orders, Bills of Materials, and Work Orders when I migrate to Xero?

Xero has no sales order, bill of materials, or work order objects, so these three entities cannot be migrated. Before cutover, you will need to decide whether to close or cancel open sales orders and work orders in SYSPRO or export them to an archive for reference before your SYSPRO licence expires. Any manufacturing or production management capability will need to be handled by a separate application integrated with Xero, which is outside the scope of the data migration ClonePartner performs.

### How do SYSPRO customers and suppliers migrate into Xero, and is there a conflict risk?

Xero uses a single Contacts object for both customers and suppliers, whereas SYSPRO stores them separately. ClonePartner maps SYSPRO AR customer records and AP supplier records into Xero Contacts, setting the IsCustomer and IsSupplier flags accordingly so that a party who appears in both SYSPRO tables ends up as one Xero contact with both roles. You should review any records where a company name appears in both your customer and supplier lists before migration, because duplicate or inconsistently named records in SYSPRO can create duplicate contacts in Xero that require manual merging after the data lands.

### What access method does ClonePartner use to extract data from SYSPRO, and does it matter which version or deployment I'm on?

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.

### How does ClonePartner handle SYSPRO GL Journal Entries, and will my full transaction history appear in Xero?

The Xero Journals endpoint is read-only via the API, which means ClonePartner cannot import individual posted journal entries as discrete line items. Instead, historical GL history is loaded into Xero Manual Journals as opening balances and period net changes, giving you a correct closing position rather than a full transaction-by-transaction ledger. If a detailed audit trail of every historical journal entry is a regulatory or operational requirement, you should export the journal history to a separate archive before your SYSPRO licence expires, as that granularity cannot be reconstructed inside Xero from the migrated data alone.

### What inventory detail from SYSPRO will I lose when stock items migrate to Xero?

ClonePartner maps SYSPRO inventory stock items to Xero Items, but Xero Items carry no warehouse location, bin, or lot or serial number detail. Warehouse quantities, lot traceability, and multi-location stock levels all exist in SYSPRO with no equivalent object in Xero. If your business relies on warehouse or lot tracking, you will need to implement a separate inventory application that integrates with Xero before you decommission SYSPRO, and you should export a full warehouse and lot report from SYSPRO at cutover for reference. That implementation work is separate from and typically longer than the data migration ClonePartner performs.

### What do I need to set up in Xero before the migrated data can be loaded?

Several SYSPRO entities depend on prerequisite records existing in Xero before dependent data can import successfully. Specifically, your chart of accounts must be in place before invoices or journals can load, tax rates must be created and matched to SYSPRO tax codes, and any currencies used in multi-currency transactions must be pre-enabled on your Xero organisation or those transactions will fail at import. Xero also rate-limits API calls per organisation, so these prerequisites affect both the sequence and the pace of the migration; ClonePartner covers the required setup checklist during the scoping call.

## 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 → Xero migration.