SYSPRO Migration Services: Choosing a Vendor-Neutral Partner

A vendor-neutral data migration partner is a firm that moves data out of SYSPRO into whichever target ERP the customer has chosen — without reselling any platform, without an implementation project to win, and without a financial incentive to steer the decision. That distinction matters because many providers that offer SYSPRO "migration services" are implementation partners whose main deliverable is the destination system, not the data move itself.

SYSPRO's licence expiry dates are 31 October 2026 for customers outside the US and 31 December 2026 for US customers. The question isn't whether you need migration help. It's whether the partner you choose is optimizing for your data or for a software deal.

This guide covers why separating data migration from implementation reduces risk, the technical constraints of extracting data from SYSPRO, and how to evaluate a SYSPRO migration partner before your expiry date.

Why SYSPRO licensing changes force a 2026 decision

SYSPRO published a formal notice on 15 July 2026 ending the Initial and Annual Licence Fee model. SYSPRO is now available only as a named-user subscription (syspro.com).

The notice sets two expiry dates for existing licences:

• 31 October 2026 for customers outside the United States.
• 31 December 2026 for customers in the US.

After your individual expiry date, "you will no longer be able to access Syspro." The notice also says an Initial License Fee "does not carry forward as a perpetual right to access the software after your expiry date" (syspro.com).

For customers who do not sign a new subscription, the notice confirms the right to export data on cessation of the licence and says SYSPRO "will provide a straightforward process for this on request." It does not describe a read-only mode, specify an export format, or say how long the export process remains available after expiry (syspro.com). That means you need to extract your data while you still have access.

This is where the partner question gets sharp. The firms that know SYSPRO best are often SYSPRO's own partners, who sell and implement SYSPRO. That creates a structural gap: the people who know your current system best have a commercial relationship with the vendor you may be leaving. ClonePartner is not a SYSPRO partner and does not resell any ERP.

What does "vendor-neutral" actually mean for data migration?

A vendor-neutral data migration partner does not resell or implement any ERP platform. It extracts data from your source system, transforms it to match the target schema, loads it, and validates the result.

This matters for three practical reasons:

No platform bias. An implementation partner's business is built around the destination ERP: its licences, configuration and rollout. Data migration is often one line inside a larger project quote, priced alongside the configuration work. A vendor-neutral partner prices the data work on its own terms — data volume, custom fields, attachment size and the platforms involved — because that is its entire deliverable.

Source-system depth. Implementation partners are experts in the target platform. They are not necessarily experts in extracting data from SYSPRO's SQL tables, plus tables, archived jobs, or lot traceability records. A migration specialist who works across many source systems builds depth in getting data out, not just in configuring the destination.

Accountability isolation. When the implementation partner also owns the data migration, a failed load gets tangled up with configuration delays, UAT overruns, and scope disputes. When the data migration is a separate engagement with its own price, timeline, and validation criteria, accountability is clear. The migration partner delivers validated data; the implementation partner configures the system. If something breaks, you know which contract to enforce.

For the full argument on splitting these roles, see ERP Data Migration vs Implementation: What's the Difference?

The two clocks: data migration vs ERP implementation

This is the distinction most SYSPRO exit projects get wrong. There are two separate workstreams with different timelines, different owners, and different skill sets:

The data migration clock is the time it takes to extract, map, load and validate your data. Most data migrations complete within 1–5 business days, depending on data volume, complexity, and API rate limits. Datasets under 10,000 records can finish in under 24 hours.

The ERP implementation clock is the time it takes to select, configure, test, and roll out the new ERP. That takes months, and your implementation partner or the ERP vendor owns it. ClonePartner does not implement ERPs.

When someone tells you "the SYSPRO migration will take six months," ask which clock they mean. If a proposal blends both, ask for the data migration to be scoped and priced on its own.

What SYSPRO-specific extraction challenges should your partner handle?

Evaluating a migration partner requires understanding how they plan to extract your data. SYSPRO 8 stores its data in Microsoft SQL Server, with one database per company plus a single system-wide database (help.syspro.com). A competent migration service will recommend the right extraction method for your deployment and the tables required.

Any partner claiming SYSPRO migration experience should be able to speak to these extraction realities without hesitation.

Direct SQL Server access

Direct SQL is the most complete extraction method. It reaches every table, including core tables such as ArCustomer, InvMaster, and SorMaster, and the plus tables that hold custom form fields.

SYSPRO's own best-practice guide warns: "Connecting to the SYSPRO databases directly using SQL drivers is not advised" (help.syspro.com). That guidance is about live integrations. For a one-off migration extract, a careful partner uses a read-only SQL login, ideally against a restored copy of the company database, so production is untouched.

OData row limits

Where direct SQL is not possible, the read-only Syspro OData Service is the next route. It "lets you connect securely to SYSPRO data without direct SQL access" (help.syspro.com). SYSPRO's 2021 R2 help says: "SYSPRO OData is a light data gathering solution. Therefore, we limit to 5000 rows under the Microsoft best practice guidelines for performance and fair use", with paging through $top and $skip (help.syspro.com). Paging through years of transaction history 5,000 rows at a time is slow, so OData is a fallback rather than the first choice for a full historical extract.

For Syspro Cloud ERP customers, SYSPRO says OData "is the only mechanism available when applications need access to SYSPRO data in the Syspro Cloud ERP environment" (help.syspro.com). Your migration partner must know how to work within OData's constraints when direct SQL is not an option.

e.net business objects

SYSPRO's e.net business objects — specifically Query objects like ARSQRY, INVQRY, and SORQRY — return XML for a single record or a filtered set. They suit integration (like connecting a third-party e-commerce site to SYSPRO), not bulk data extraction. A partner who proposes e.net as the primary extraction route for a full data migration has not thought through the volume.

Business Activity Queries (BAQs)

SYSPRO Business Activity Queries "are SQL views that are created in the relevant company databases", and "any SQL user with db_datareader permissions can retrieve data using the views" (help.syspro.com). They are useful for reporting. They are views over the data, so a partner still needs to confirm they cover every table and plus table in scope.

Plus tables and custom fields

SYSPRO stores custom form data in plus tables: data for the ArCustomer table lives in a table named ArCustomer+ (help.syspro.com). These are often where the most business-critical data lives — fields your team added because the standard schema didn't cover your process. A migration partner must extract plus tables alongside their parent tables and map those custom fields to equivalents in the target system. If your partner's scoping call doesn't ask about plus tables, that's a red flag.

For a deeper dive, see Migrating SYSPRO Custom Form Fields and Plus Tables.

Archived data

SYSPRO has its own archiving for sales orders, jobs, and ECC bills of materials, which copies purged data to XML files. SYSPRO 7 Update 1 help notes: "No 'additional' attached information (such as custom forms, multimedia, notes, etc) is archived" (help.syspro.com). That history sits outside the live tables. Your partner should ask about archive files during scoping, because records found late extend the work.

For a full walkthrough of extraction methods, see How to Export Data from SYSPRO: Methods, API Limits & Portability. For the SQL table structure itself, see SYSPRO SQL Table Map for Data Migration.

How to evaluate a vendor-neutral data migration partner

Here is a practical checklist for evaluating partners. These criteria reflect what determines whether a SYSPRO data migration succeeds or stalls.

1. Do they price the data migration separately?

A fixed price for the data migration, separate from any implementation work, is the clearest signal of a vendor-neutral partner. If the migration cost is buried inside a larger implementation quote, you can't see what you're paying for the data work. Hourly billing has a different problem: the provider's technical hurdles become your cost.

ClonePartner charges one fixed price per project, starting at $500 (clonepartner.com), with no hourly billing and no per-record metering. Price scales with data volume, custom fields, attachment size, and the platforms involved.

2. Do they validate data, not just move it?

Spot-checking a few records in the user interface is not enough for ERP data. Ask specifically about:

• Record-count parity — does the count in the target match the source after filtering?
• Field-level validation — are values preserved through transformation, especially currencies, dates, and decimal precision?
• Referential integrity checks — do foreign keys resolve? Does every sales order line reference a valid customer and item?
• Reconciliation reports — do you get a documented comparison of source vs. target that your finance team can sign off on?

Ask to see the checks themselves rather than accepting a promise of accuracy.

3. Do they handle the full SYSPRO entity landscape?

SYSPRO's data model spans customers, suppliers, inventory, BOMs, routings, GL accounts, sales orders, purchase orders, lot traceability, serial tracking, WIP, and job history. A partner who only quotes for master data and ignores transaction history, lot traceability, or BOMs is leaving gaps that will surface in production.

Ask for the entity list they plan to migrate and compare it against your actual SYSPRO usage. For guidance on what to include, see What Data Should You Actually Migrate to Your New ERP?

4. Do they offer unlimited sample migrations?

Data mapping is an iterative process. Your first attempt at mapping SYSPRO's InvMaster to a new system will likely reveal edge cases you didn't anticipate, and manufacturing data like multi-level BOMs or lot traceability records rarely maps cleanly on the first pass.

A sample migration on a subset of real data — not a demo, not a slide deck — is the only way to verify mapping accuracy before committing. ClonePartner runs unlimited sample migrations before the full run.

5. Do they plan for cutover, not just bulk load?

The bulk load should run in the days before go-live, while SYSPRO stays live. SYSPRO freezes before Monday's working day starts. A final delta — covering only the records that changed — takes about 30 minutes.

Go live on a Monday, never on a Friday. If your partner doesn't describe a cutover plan that keeps SYSPRO running until the freeze, ask them to.

6. Can they show security credentials?

Extracting your ERP database means handling your most sensitive financial and customer data. Ask for evidence, not promises. ClonePartner holds SOC 2 Type II and ISO 27001, and purges staging data within 30 days of project close.

Red flags when choosing a SYSPRO migration partner

Red flag	Why it matters
Migration cost is bundled into the implementation quote	You can't evaluate the data work separately. The migration becomes tied to the implementation timeline.
Partner only supports one target ERP	They have a financial incentive to push you toward that platform, regardless of fit.
No mention of plus tables or custom fields in scoping	They'll discover these late and the timeline will slip.
Flat CSV exports as the whole plan	Flat files lose the links between tables, such as BOM parents and components, unless the partner rebuilds them. Ask how they will.
No sample migration offered	You're committing to a full migration without evidence that the mapping works.
Timelines quoted in months for the data migration alone	The data migration takes days. A quote in months is blending it with the implementation.
No independent security audit	SOC 2 Type II and ISO 27001 are reasonable baselines for handling production ERP data.

When should you start scoping a SYSPRO migration?

Now. If you are outside the US, your licence expiry date is 31 October 2026. If you are in the US, your license expires on 31 December 2026. Either way, raise the data export with SYSPRO before your expiry date.

The data migration itself completes in days. The scoping call, entity mapping, and sample migration cycles still need some lead time, and so does coordination with your implementation partner. Early scoping often surfaces data quality issues that affect the implementation too, so the two workstreams can run in parallel.

SYSPRO's formal notice asks customers to raise the data export "with your account manager ahead of" the expiry date (syspro.com). Don't wait for that process to finish before engaging a migration partner. If you run SYSPRO on-premise with SQL access, a partner can take a read-only extract while you still have access.

For the full pre-exit checklist, see SYSPRO Exit Checklist: What to Do Before Your Licence Expires.

What does a vendor-neutral SYSPRO migration cost?

ClonePartner charges one fixed price per project, starting at $500 (clonepartner.com). The price scales with data volume, custom fields, attachment size, and the platforms involved. There is no hourly billing and no per-record metering. The ERP implementation is priced separately by whoever does it.

For a detailed breakdown, see What a SYSPRO Data Migration Costs in 2026.

Choosing the right partner for your target platform

One advantage of a vendor-neutral partner is target-platform flexibility. Whether you're moving to Dynamics 365 Business Central, Epicor Kinetic, SAP Business One, Oracle NetSuite, Sage X3, or Acumatica, the extraction side stays the same — the same SYSPRO SQL tables, the same plus tables, the same lot traceability records. What changes is the target-side loading: each platform has its own import tools, APIs and validation rules.

A vendor-neutral partner handles both sides. ClonePartner's pair pages cover specific paths, such as SYSPRO to Microsoft Dynamics 365 Business Central, SYSPRO to Oracle NetSuite and SYSPRO to Epicor Kinetic.

We've also published technical guides for several common SYSPRO migration paths:

• SYSPRO to Dynamics 365 Business Central Migration Guide
• SYSPRO to Epicor Kinetic Migration: A Technical Guide
• SYSPRO to SAP Business One Migration: A Technical Guide
• SYSPRO to Oracle NetSuite Migration: A Technical Guide
• SYSPRO to Sage X3 Migration: A Technical Guide

Why engineering-led services beat off-the-shelf ETL tools

Off-the-shelf ETL (Extract, Transform, Load) tools require you to build the data pipelines, handle the API rate limits, and write the transformation logic yourself. If you lack in-house data engineers familiar with SYSPRO's schema, these tools are a liability, not a shortcut.

ClonePartner is a vendor-neutral, engineer-led data migration service. Engineers own each project from scoping to cutover. We move the data out of SYSPRO into whichever system you choose and validate it with record-count parity, field-level checks and reconciliation reports.

Making the call

The decision comes down to this: do you want your data migration owned by the firm whose main deliverable is your destination system, or by a team whose only deliverable is accurate, validated data in that system?

Both models can work. But when the SYSPRO deadline is fixed, the target platform is already chosen, and the implementation partner has their hands full with configuration and UAT, a dedicated, vendor-neutral migration partner takes the data risk off the critical path.

If you are working through the 2026 SYSPRO licensing changes, separate the migration from the implementation. Choose a partner who treats data integrity as an engineering discipline.