You use the Database Administration tool to migrate your version 19.8 data (including all company data in folders and subfolders of …\MB7\[CompanyName]) to the current version. The migration process automatically creates a new SQL Server database and stores your migrated SQL data in a new location.
Your original data remains intact and available in version 19.8.
You can migrate data to version 26.1 only from version 19.8. If your company databases are in an earlier version of Sage 100 Contractor, you must upgrade them to version 19.8 first.
Migrated files are located in shared folders under C:\Sage100Con\Company\[Company Name]. (Users navigate to the \Sage100Contractor\[Company Name] on the server.) Subfolders are organized using a similar folder structure as in earlier versions, and include:
- Aatrix Forms
- Attachments
- Direct Deposit
- Images
-
Reports
Note: The Direct Deposit and Reports folders are available as soon as you open the company in Sage 100 Contractor. The remaining folders are created as needed.
Migrating shared custom reports
If you customized any of the reports that came with version 19.8, you need to migrate them to version 26.1, also.
Note: If you created custom reports using third-party applications, you must use the report views to adapt them, separately, for Sage 100 Contractor 2024.
Private custom reports
In version 19.8, private reports were stored on individual workstations with each user’s Windows application data, and therefore cannot be migrated along with the shared custom reports.
In version 26.1, when a user logs into Sage 100 Contractor, the server checks their Windows User Data folder to see if they have any private Sage 100 Contractor. If they do, the program creates a User Data folder on the server for that user’s Windows ID, and copies their reports to this folder.
Note: The Backup program backs up private reports and other user-specific data for each user. However, the Restore program does not restore them. If a user somehow loses their private reports, you can retrieve them by navigating to a recent backup file (in the local Backup folder) and extracting the user’s data folder.
Changes to converted data
During migration, the program may encounter problems in that might prevent it from writing a particular record to the SQL database.
If the problem is one that the migration program can fix, it changes the record, and then writes the updated record to the SQL database.
However, not all errors can be fixed. In these cases, the record is not written to the new database.
The migration log file
The program keeps a log of all changed (fixed) records and records that were not migrated because of an unresolvable error, unless the record was invalid in version 19.8. Invalid records are neither migrated nor logged.
Important! After migration, you should check the log file to see what changes were made to your data during conversion, or whether any records were not migrated to the new SQL database.
The _SQL_MIGRATION_LOG.TXT file is located in the source company's main folder (for example, C:\MB7\Sample Company). A supplemental file, _SQL_MIGRATION_LOG_VERBOSE.TXT, includes more detailed information about each error found.
After migrating company data and reports
After migrating your data, you will likely need to perform the following additional steps to prepare your company for use in Sage 100 Contractor:
- Add company administrators. There is no longer a generic "supervisor" user as there was in version 19.8. All users must sign into the company using their personal IDs, and only users designated as company administrators have heightened privileges previously associated with the "supervisor" role. You can designate one user as a company administrator during migration, but you can add others later.
-
Add SQL logins for new users. If you have new users that did not exist in your version 19.8 company, add them as users to the SQL database.
You must also add them as users and assign security in Sage 100 Contractor.
-
Designate an additional SQL Server administrator. Only a user with a 'sysadmin' role can administer users for SQL Server and assign the 'sysadmin' role to another user. Therefore, it is vital at all times that more than one user has a 'sysadmin' server role. If the principal system administrator should suddenly fall ill, or leave your company, or otherwise be unable to perform their duties, another person with administrative access to the SQL Server database must be able to take over that role.
Note: The person who installs Sage 100 Contractor is automatically assigned a 'sysadmin' role.
-
Migrate scheduled reports and alerts. You must use Sage 100 Contractor to migrate tasks scheduled in version 19.8 for individual workstations. When you open the 7-5 Scheduled Reports Manager window or the 7-6 Alerts Manager window, Sage 100 Contractor checks whether any scheduled reports or alerts exist, respectively, for version 19.7. If it finds any, it displays a migration window that you can use to migrate these tasks to the current version. For more information, see the help for these windows in the Sage 100 Contractor application.
-
Claim Supervisor process maps. If process maps existed for the Supervisor user in version 19.8, Sage 100 Contractor will attempt to assign them automatically to users that log in to Sage 100 Contractor until the process maps are claimed.