The first question before moving Sage 100 to a new server is not: “How fast is the new server?”
It is:
Start With the Sage Version
The version tells us what installation and conversion path we are dealing with.
An older MAS 90, MAS 200, or Sage 100 environment can have a very different migration path from a relatively current Sage 100 release.
Then Inventory the Dependencies
We want to identify the things that quietly rely on the current environment:
- Custom reports and forms
- Paperless Office archives and email delivery
- Visual Integrator jobs
- ODBC connections
- Shipping, warehouse, EDI, tax, and other integrations
- Payroll
- User workstations or remote desktops
- Custom panels and scripts
- Printing
- Historical environments
Understand How Users Reach Sage
Some companies work on a local network.
Others use Remote Desktop, hosted servers, cloud environments, or mixed models.
The migration needs to reflect the way the users actually work.
Backups Come Before Courage
Before production cutover, we want a known-good backup and a rollback plan.
Who takes the backup?
Has it been verified?
Where is it stored?
What would cause us to roll back?
Who makes that decision?
The answers should exist before the migration window starts.
Test the Business, Not Just the Login Screen
A user opening Sage successfully does not prove the migration is complete.
We want representative users to test the workflows they actually perform: posting, reports, forms, printing, Paperless Office, integrations, Payroll, warehouse activity, and whatever else is important to that company.