Sage 100 Version Upgrade and Data Migration Checklist
This checklist covers moving Sage 100 Standard, Advanced or Premium to a new major version (for example 2023 or 2024 to 2025) with a parallel install and the Parallel Migration Wizard. It focuses on what breaks: enhancements, Custom Office, scripts, forms and integrations.
0 of 32 items complete
8 critical items still open - these are the highest-risk gaps.
1. Plan
2. Install
3. Migrate
4. Test
5. Go-live
Critical items are the ones that most often stop a Sage 100 upgrade: wrong upgrade path, uncertified enhancements, panel customizations and integrations still pointing to the old home path.
Planning a Sage 100 upgrade?
Send us your current version, enhancements and integrations and we will flag what needs attention before you migrate.
Optional. The tool and every export work without this. No spam.
How to use it
Work through the five groups in order and give each item an owner. Start the Plan group weeks before the install, because third-party enhancement versions and the supported upgrade path decide whether the project can happen at all. Run the Migrate and Test groups at least once against a copy before the real go-live weekend; most issues show up in the first trial migration. Export the checklist to PDF and keep it with the version numbers you installed.
Parallel install and migration
Sage 100 major versions install side by side: the new version goes into its own folder, and the Parallel Migration Wizard copies system and company data from the old installation. The old version keeps working until you switch users over, which gives you a rollback path and lets you run trial migrations. After migration, each company is converted to the new data format in Company Maintenance. Custom Office panels come forward with the Customizer Update Utility, and Crystal forms with the Crystal Report Conversion Wizard. Check the exact steps in the Installation and System Administrator's Guide for your target version.
- Old install stays live until go-live.
- Run at least one trial migration.
- Convert data per company after migrating.
Worked example: integrations
A company runs a BOI script that creates sales orders from a web store, using the home path C:\Sage\Sage 100 2024\MAS90\Home. After migration to a new folder for the target version, the script still points at the old path, so orders keep landing in the old version. The test group catches it: repoint the Init path, run a test order, and update ODBC data sources the same way.
Gotchas
An enhancement that is not certified for the target version is the most common blocker, so ask early. Panel customizations that were never documented come forward only partly; test every customized screen. Scripts must be recompiled after migration. Install the workstation on every client, because older workstation installs cannot connect to the new server version. Premium needs a supported SQL Server version on the server before you start.
Frequently Asked Questions
Can I upgrade Sage 100 directly from 2023 to 2025?
That depends on the migration paths Sage supports for the target release, which are listed in its Installation and System Administrator's Guide. Most recent releases migrate directly from several prior versions, but older installs may need an intermediate step. Check the guide for the exact source versions before planning, and confirm every enhancement is certified for the target.
What is the Parallel Migration Wizard in Sage 100?
It is the utility, run from the new installation, that copies system and company data from an existing Sage 100 installation into the new one. Because the new version is installed in parallel, the old installation stays usable, which allows trial migrations and a rollback path. After migrating, convert each company's data in Company Maintenance.
How do I install the Sage 100 workstation?
After the server install and product update, run the workstation setup from the server's installation share on every client that will use Sage 100, then launch it once to confirm it connects. Workstations must match the server version and product update. For Premium, the workstation also needs network access to the SQL Server.
What happens to my Custom Office customizations when I upgrade?
Panel customizations, UDFs and scripts come across with the data, but panels must be brought forward with the Customizer Update Utility and scripts recompiled. Panels Sage changed in the new version may lose some modifications or raise Error 65. Test every customized screen and keep screenshots from the old version for comparison.
If you want a private AI layer on your upgraded Sage 100 that answers questions about orders and stock on your own servers, we can add it once the upgrade is stable.
Related Tools
Sage 100 Year-End Close Checklist (Module Order SO, PO, IM, AR, AP, GL)
Step-by-step year-end list for Sage 100 2022 to 2025: what to back up, which reports to keep, how to handle 1099s and the order to close each module.
Other ERPsSage 100 ProvideX Error Codes Reference (Error 12, 43, 65, 88, 200)
Searchable list of the ProvideX run-time errors Sage 100 users actually see, with the exact message text, the usual Sage 100 cause and the first check to run.
Other ERPsSage 100 Business Object Interface (BOI) Sales Order Script Generator
Produces a working PowerShell script that logs in to Sage 100 through BOI, creates a sales order with one line and reports Sage's own error message on failure.
Other ERPsSage 100 User-Defined Script Generator (VBScript UDS)
Builds a working Sage 100 Advanced or Premium user-defined script that looks up the customer, copies the credit hold flag into a UDF and optionally stops the save.
More Other ERPs tools
See all- Sage 100 Table and Module Prefix Reference
- Infor VISUAL Work Order Status and Structure Reference
- Infor VISUAL Manufacturing Scheduling Checklist
- Infor XA (MAPICS) Period End Close Checklist
- Infor VISUAL Database Table Reference
- Infor XA (MAPICS) Application Module Reference
- IBM i Commands for Infor XA Administrators Reference
- Acumatica Generic Inquiry Design Template
- Acumatica Manufacturing Edition Setup Checklist
Keep exploring
Free tools
- Sage 100 to Cloud Migration AssessmentA 10-question readiness score for companies on Sage 100 deciding when and how to move to a cloud ERP, with recommendations by result band.
- Sage 100 Year-End Close Checklist (Module Order SO, PO, IM, AR, AP, GL)Step-by-step year-end list for Sage 100 2022 to 2025: what to back up, which reports to keep, how to handle 1099s and the order to close each module.
- Sage 100 Table and Module Prefix ReferenceFind the Sage 100 module prefix and the commonly used table names for items, customers, vendors, orders and bills of material.
ERP fixes and how-tos
- How to Add AI to Sage 100 and Sage 300 On-PremPrivate AI architecture for on-prem Sage 100 and Sage 300: ODBC or SQL extracts, Sage 300 Web API, Sage 100 BOI, local GPU model, permissions and audit log.
- Sage X3 latest version and release historySage X3 version lineage from V5 to V12 and later, the Sage Enterprise Management name, and how to check your own version and plan an upgrade.
- How to Add User Defined Fields (UDFs) in Sage 100How to add a user defined field in Sage 100 with Custom Office, place it on a panel, and expose it to reports, ODBC and imports, with the usual UDF pitfalls.
AI on your ERP
- AI for Sage 100 Small Manufacturers: Practical Answers From Work Orders, BOMs and InventoryPractical AI for small manufacturers on Sage 100: ask about work orders, BOMs, stock and shortages in plain English via ODBC or SQL, kept on a small server.
- AI for Sage 100, Grounded in Your MAS90/200 DataPut AI on Sage 100 and the Sage 100 Manufacturing (MRP) data set without sending data to a public model. Private LLMs and agents grounded in your MAS90/200 tables.
Integrations
- How to use ChatGPT with Sage 100How to use ChatGPT with Sage 100: exports versus live access, custom GPT actions, enterprise data controls, and when a private model is the safer choice.
- How to use Claude with Sage 100How to use Claude with Sage 100 through an MCP connector, the Anthropic API, Bedrock or Vertex, and what to do when the data must stay on-prem.