--- title: "SYSPRO to Katana Migration | ClonePartner" description: "SYSPRO to Katana: Inventory Warehouses → Locations: Set up in Katana before stock is loaded. Engineer-led, zero downtime." source: SYSPRO target: Katana canonical: "https://clonepartner.com/migrate/syspro-to-katana" --- # SYSPRO → Katana migration Engineer-led SYSPRO to Katana data migration. Move customers, suppliers, items and open orders out of SYSPRO into Katana, cloud inventory and manufacturing software for product businesses. ## Entity mappings - **Customers** (SYSPRO) → **Customers** (Katana) - **Suppliers** (SYSPRO) → **Suppliers** (Katana) - **Inventory (Stock Items)** (SYSPRO) → **Products and Materials** (Katana) - **Bills of Materials** (SYSPRO) → **BOM rows** (Katana) - **Sales Orders** (SYSPRO) → **Sales Orders** (Katana) - **Purchase Orders** (SYSPRO) → **Purchase Orders** (Katana) - **Work Orders** (SYSPRO) → **Manufacturing Orders** (Katana) - **Lot Tracking** (SYSPRO) → **Batches and serial numbers** (Katana) - **Inventory Warehouses** (SYSPRO) → **Locations** (Katana) - **Customer Contacts** (SYSPRO) → **Customer addresses** (Katana) - **AR Invoices** (SYSPRO) → **Not available** (Katana) - **AP Invoices** (SYSPRO) → **Not available** (Katana) - **General Ledger Accounts** (SYSPRO) → **Not available** (Katana) - **GL Journal Entries** (SYSPRO) → **Not available** (Katana) ## 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 AR and AP invoices when I move from SYSPRO to Katana? Katana has no invoice object, so AR invoices and AP invoices cannot be migrated into it at all. Those records stay in SYSPRO or move into your connected accounting system (such as QuickBooks or Xero) through a separate accounting migration that ClonePartner does not perform. Plan which system holds your invoice history before cutover, because nothing in this migration carries it across. ### Do I need to set up Katana locations before ClonePartner loads my SYSPRO warehouse stock? Yes. SYSPRO warehouse records map to Katana Locations, but Katana requires the location records to exist before stock quantities can be assigned to them. You must create the corresponding Locations in Katana ahead of the migration run; ClonePartner then loads inventory against those locations during the stock import. If the locations are missing, the stock import will fail or land without a location assignment. ### What should I do with open SYSPRO work orders before migration? SYSPRO Work Orders map to Katana Manufacturing Orders, but the mapping is a workaround that requires open jobs to be closed in SYSPRO before cutover. Any work order left open at migration time cannot be reliably represented in Katana's Manufacturing Order model, and attempting to carry it across risks incomplete or inconsistent production data. Close or cancel all open jobs in SYSPRO during your pre-migration preparation window, then recreate any genuinely in-flight orders manually in Katana after go-live. ### Will my SYSPRO custom form field data come across to Katana? SYSPRO stores custom form fields in separate plus tables—for example, customer extensions live in [ArCustomer+] rather than the main customer table. ClonePartner extracts these plus tables separately and maps them during scoping, but Katana's data model may not have a direct equivalent field for every custom attribute. Any custom data that has no target field in Katana will be identified in the pre-migration field mapping review, giving you the opportunity to decide how to handle it before the migration runs. ### How does ClonePartner access SYSPRO data, and does it matter whether I'm on SYSPRO on-premises or SYSPRO Cloud ERP? 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 are SYSPRO contact records handled, and can I lose contact data silently during migration? Katana holds contact details directly on the customer record rather than as standalone contact objects, so SYSPRO customer contacts are migrated as fields on the corresponding Katana customer rather than as separate entries. If a SYSPRO customer has multiple contacts, only the data that fits the Katana customer address model can be carried across; secondary contacts and any contact-level custom fields stored in SYSPRO plus tables do not have a native home in Katana and would otherwise be dropped without explicit planning. ClonePartner flags these one-to-many contact situations during field mapping so you can decide before the migration runs whether to consolidate, append to a notes field, or export the overflow contacts separately. ## 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 → Katana migration.