Documentation:

• Before attempting any installation or upgrade, be sure to review the following documents to ensure a smooth installation. These documents can be found in the Sage Knowledgebase or Sage 100 Documentation website
• Please Note:
  • Sage 100 Customer Support can provide suggestions and assist with specific error messages that you may encounter
    • Sage 100 Customer Support does not walk a customer over the phone through the entire planning, preparation, backup, rebuild, installation, migration, conversion, etc. process, as this may take several hours or more
      • See Sage Business Care Support Services for the complete scope of Sage 100 Customer Support
  • The steps that you follow may have to vary based on your situation. This article describes the documents and resources available to you
  • Based on the relevant Supported Platform Matrix for the version of Sage 100 you intend to install, you may have to consider hardware and/or operating system upgrades
  • For a potential upgrade that involves hardware/operating system migration, that may span multiple versions, that may involve third-party enhancements or customizations (which we do not assist with), we highly recommend working with an experienced local business partner
  • In order for any links in this article to be valid, you must first log into the Sage Support Portal and then click the applicable link below. Some of these documents can also be found in the "Documents" folder within the Sage 100 installation download (after the compressed download file has been extracted).

1. Installation and System Administrator's Guide:
   This guide provides the information necessary for installing Sage 100. This guide also contains information and troubleshooting tips on the configuration of the various operating systems and environments in which the Sage 100 software is supported.
   • Note: Refer to  Sage 100: Download Portal and select the applicable Sage 100 version to download the Installation and System Administrator's Guide.
   • Note: A copy of the Installation and System Administrator's Guide document can be found in the "Documents" folder, in the Sage 100 installation files (from where one would install Sage 100).
2. Upgrade Guide:
   This document provides information on the changes to expect after upgrading to a new version of Sage 100. This guide also includes Pre-upgrade checklists, Upgrade Checklists and Data Conversion Checklists.
   • Note: Refer to Sage 100: Download Portal and select the applicable Sage 100 version to download the Upgrade Guide.
   • Note: A copy of the Upgrade Guide document and the Upgrade Checklist document can be found in the "Documents" folder, in the Sage 100 installation files (from where one would install Sage 100)
   • Note: If you come across instructions to run the Parallel Migration Wizard (migrate.exe), note that you MUST run it from within the new (destination) installed location, NOT from within the previous (source) installed location.
3. Supported Platform Matrix:
   System compatibility information and requirements for the supported versions of Sage 100 Standard, Sage 100 Advanced and Sage 100 Premium. Always review this document prior to any changes to Sage 100 or the operating system. The Matrix is updated when a new version is released or when a major operating system is upgraded or released.
   • Note: Refer to Supported Platform Matrices (SPM) for Sage 100; System requirements and specifications and select the desired Sage 100 version.
4. Integrated Solutions Compatibility Matrix:
   Guides to Sage 100 compatibility with Aatrix, Avatax, Sage CRM, Sage Abra, Sage HRMS, Crystal Reports, SalesLogix, Sage Fixed Assets, Microsoft Office, Sage Payment Solutions, Sage Intelligence, Payroll Services, and Credit Card Processing.
   • Note: Refer to Integrated Solutions Compatibility Matrices (ISCM) for Sage 100 and select the desired Sage 100 version.

____________________________
Upgrades (Parallel vs. In-Place):
Note: Beginning with versions 4.40 and higher, In-Place upgrades are no longer available as an option.

Note: When the option exists, a Parallel upgrade is almost always recommended rather than an In-Place upgrade.

• A Parallel upgrade is defined as the process of installing the new version to a different location than the prior version, then migrating the data to the new installation. It requires much more disk space than an In-Place upgrade and requires more steps, but is much less disruptive if the upgrade fails. The data can be easily accessed and repaired on the prior version, and users can continue to work in the prior version until any issues are resolved. A Parallel upgrade also allows the new version to be tested prior to committing to the final upgrade. Due to the complexities of the data conversions, the ability to access the data in the prior level is imperative.
• An In-Place installation is defined as the process of installing Sage 100 directly over a prior version. It can be more convenient because it requires less disc space and requires fewer steps, but can cause more work if the upgrade fails. Always make a backup prior to an In-Place upgrade. As mentioned, the in-place option is no longer available for upgrades to version 4.40 or higher.
• IMPORTANT: When migrating data, you must run the Parallel Migration Wizard (migrate.exe) from within the new (destination) installed location, NOT from within the previous (source) installed location - the wizard will ask you for the source location. DO NOT migrate from an installation into itself: you will lose system data files, be unable to log into Sage 100, and restoration from backup will be your only option.

_________________________________________________________________________________

Minimum version needed to upgrade to version 2018 and higher (and special considerations):

• Sage 100 (formerly Sage MAS 90 or 200) version 4.50.8.0 is the minimum required version needed to upgrade to Sage 100 2018 or higher.
  • Note: The TimeCard application module is not compatible with the initial release of Sage 100 2018.
    • When migrating with TimeCard installed in the source installation, the process will stop and recommend removal of the TimeCard module. You cannot do that without losing TimeCard module data and history. You may want to wait until the targeted 2018 product update is released.
  • Note: If a Multi-Bin Management enhancement (from DSD/ScanForce) is installed and used in the source installation, do not migrate to Sage 100 2018 until the update for that application becomes available. Other third-party enhancements may have similar stipulations. Check with your provider.
  • Note: Because version 4.50.8.0 is no longer available to download from the Sage Knowledgebase, if you are on versions 3.71 through 4.40, you can alternatively upgrade to version 2017, and then upgrade to version 2018 or higher.
    • Note: Sage 100 2017 is retired as of September 30, 2020, and thus downloads for Sage 100 2017 Full Product and Sage 100 2017.6 (Product Update 6) may no longer be available on the Sage Knowledgebase. You may want to check with your Sage business partner for a copy.
    • Note: Sage 100 2018 is retired as of April 22, 2021, and thus downloads for Sage 100 2018 Full Product and Sage 100 2018.10 (Product Update 10) may no longer be available on the Sage Knowledgebase. You may want to check with your Sage business partner for a copy.

_____________________________________________________

Product Registration Keys, Modules, and Sample Companies:

• Modules or applications that can be installed will be determined by the Product Key entered during the installation and registration process.
  • Product Registration Keys: These consist of a Serial Number, Customer Account Number (10 digits, begins with "400"), User or Unlock Key, and Product Key (5 sets of 5 alphanumeric characters).
    • For more information, refer to How to register Sage 100 or How to find, register or enter product registration keys for Sage 100 user licenses and application modules
  • If an Application Module is NOT Selected: Some modules may still be installed even when they are not valid for the registration keys entered. However, there will be a time-limited Trial Period that will expire. This may create problems if processing in already-purchased modules relies on the inclusion of a time-limited module when the trial period expires.
  • If an Application Module is installed in a previous version, but not installed in the new version, you may encounter a migration error message informing you that you will need to remove the module data and uninstall the unused module in the previous version, prior to migration.
  • Payroll: For those who use the Payroll module, you must first have an active and current Payroll Subscription Plan with the correct product registration keys applicable to the number of employees (Payroll Tier).
    • Note: For more information, refer to How to register Sage 100 or How to find, register or enter product registration keys for Sage 100 user licenses and application modules
• Sample companies, also known as demonstration data, are also available for installation. Sage Customer Support recommends installing sample companies for testing and training purposes.

__________________________________
Product Updates and Program Fixes

• In addition to full version releases of Sage 100, Sage also releases regular Product Updates and individual Program Fixes. Sometimes, a Product Update is released on the same day as a version is initially released. Therefore, make sure to check the Sage Knowledgebase for Product Updates and Program Fixes, and install them FIRST, prior to migrating to, or converting data in, the new installation.
• In some versions, installing a Product Update (and possible program fixes) is mandatory prior to migrating and converting data from a previous version. Otherwise, the migration or conversion may not only fail, you may have to uninstall the new version and reinstall properly with both the Full Product and then the Product Update before you can migrate and convert again.
  • Example: Sage 100 2014 and Sage 100 2015 each had a mandatory Product Update 1 that was released at the same time.
  • Note: Sage 100 2016, 2017, 2018, 2019, 2020, and 2021 all did not have a Product Update released at the same time as the full products were released. However, if there are any available updates, it is still important to install them.
• If you have third-party enhancements (e.g. custom programming from a Sage developer) then you need to check to see if their product is compatible with a Product Update or program fix, or if they have an update to their third-party product that is needed to be compatible.

• Payroll - For those with Payroll who are upgrading to versions 2018 or higher, note that Payroll is now a separate download and install. So after installing the Sage 100 Full Product and a current Product Update, there would be a third download and install for Sage 100 Payroll. If you do not install Payroll for Sage 100, then Payroll will not be installed and you will not be able to migrate or convert data.
• TLS - Sage 100 2018 and below uses TLS (Transport Layer Security) 1.0. Sage 100 2019 and higher uses TLS 1.2. As of the year 2020, many providers have stopped (or will soon stop) supporting TLS 1.0 and 1.1. This include SMTP (e-mail) services and Sage 100 Payroll's tax calculation (as of August 2020). The Payroll version must be 2.19.0 or higher.
• Premium - For those considering upgrade from Sage 100 Standard or Sage 100 Advanced to the Sage 100 Premium product, note that some application modules like Work Order are NOT available in the Sage 100 Premium product.
• Multiple Installations - You can really only have one version of Sage 100 installed on a server. Ideally, that server should be a dedicated server.
  • Example: You cannot have two installations of Sage 100 2020 on the same server.
  • Example: You could have an installation of Sage 100 2018 and a separate installation of Sage 100 2019 on the same server, though each should be installed to a separate locations. If you install the Workstation Setup client install on the server for each version, make sure they are to different locations as well.
  • Example: If you have Sage 100 2017 or below on a server, and install Sage 100 2018 or higher, their versions of the Crystal Reports runtime engines are not compatible, and may break report printing for the prior version.