--- title: "SYSPRO to Fishbowl Migration | ClonePartner" description: "SYSPRO to Fishbowl: Work Orders → Manufacture Orders: Close open SYSPRO jobs before cutover. Engineer-led, zero downtime." source: SYSPRO target: Fishbowl canonical: "https://clonepartner.com/migrate/syspro-to-fishbowl" --- # SYSPRO → Fishbowl migration Engineer-led SYSPRO to Fishbowl data migration. Move customers, suppliers, items and open orders out of SYSPRO into Fishbowl, inventory and manufacturing software that works with QuickBooks and Xero. ## Entity mappings - **Customers** (SYSPRO) → **Customers** (Fishbowl) - **Suppliers** (SYSPRO) → **Vendors** (Fishbowl) - **Inventory (Stock Items)** (SYSPRO) → **Parts and Products** (Fishbowl) - **Bills of Materials** (SYSPRO) → **Bills of Materials** (Fishbowl) - **Sales Orders** (SYSPRO) → **Sales Orders** (Fishbowl) - **Purchase Orders** (SYSPRO) → **Purchase Orders** (Fishbowl) - **Work Orders** (SYSPRO) → **Manufacture Orders** (Fishbowl) - **Inventory Warehouses** (SYSPRO) → **Locations** (Fishbowl) - **Lot Tracking** (SYSPRO) → **Tracking (lot and serial)** (Fishbowl) - **AR Invoices** (SYSPRO) → **Not available** (Fishbowl) - **AP Invoices** (SYSPRO) → **Not available** (Fishbowl) - **General Ledger Accounts** (SYSPRO) → **Not available** (Fishbowl) ## 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 invoices, AP invoices, and general ledger accounts when I move from SYSPRO to Fishbowl? None of these three entities move into Fishbowl because Fishbowl has no general ledger, and invoices and bills live in the accounting file you connect to Fishbowl (QuickBooks or Xero). Your accounting history stays in SYSPRO or your existing accounting platform and should be handled separately as part of your broader replatform project. ClonePartner migrates the operational data — customers, vendors, parts, orders — but the ledger side is out of scope for what we move. ### How do open work orders in SYSPRO get handled, and what do I need to do before cutover? SYSPRO Work Orders map to Fishbowl Manufacture Orders, but this is a workaround path, not a direct import. You should close or complete any open production jobs in SYSPRO before cutover, because in-progress work order state does not transfer cleanly and will need to be recreated manually in Fishbowl as Manufacture Orders. Any jobs you cannot close before cutover should be documented so your team can re-enter them in Fishbowl after the data lands. ### Do SYSPRO custom form fields migrate to Fishbowl? Custom form fields in SYSPRO are stored in separate plus tables — for example, customer custom fields live in [ArCustomer+] rather than [ArCustomer] — so they require explicit extraction and mapping steps beyond the standard entity pull. ClonePartner extracts these separately during scoping, but whether a given custom field has a corresponding home in Fishbowl depends on your Fishbowl configuration; fields with no target destination will be flagged during validation and may need to be mapped to custom fields you set up in Fishbowl in advance. ### What API or server access does ClonePartner need on the SYSPRO side before the migration can start? 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. ### What do I need to set up in Fishbowl before the imported data can load correctly? Several Fishbowl entities must exist before dependent records can import: warehouse Locations need to be configured before inventory quantities can be assigned, and tax codes and default accounts in the connected QuickBooks or Xero file must be in place before customers and vendors load without errors. Customers, Bills of Materials, and Sales Orders enter Fishbowl through CSV import rather than the REST API, so the CSV column format must match the version-specific template documented on your own Fishbowl server. Completing these prerequisites before we begin the live migration run prevents import rejections and avoids a second pass. ### If I run SYSPRO across multiple companies, does the migration cover all of them? Each SYSPRO company has its own separate SQL Server database, so multi-company environments require a company-by-company extraction pass rather than a single pull. During scoping we confirm how many company databases are in scope, because each additional company adds to the data volume and may affect the timeline estimate. You should also confirm that the database access you provide covers each company database in scope, not just the primary one. ## 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 → Fishbowl migration.