About migrating your data from version 19.8
Migrating company data
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.
Before migrating
Migration should proceed smoothly in most instances. However, you should perform the following audits in version 19.8, and then fix any errors, before attempting migration:
- 1-6 Period and Fiscal Year Management > Audit Books
- 5-3-7 Payroll Audit
- 6-6-3 Purchase Order Audit
- 6-7-4 Subcontract Audit
- 12-5 Inventory Audit
In addition, to ensure that all records exist and are properly indexed:
-
In the 7-4 Rebuild Indexes window, rebuild indexes.
-
In the 1-8 General Ledger Setup window, verify that all the required accounts exist.
-
In the 6-5 Cost Codes window, make sure that all cost codes are assigned to a cost division.
Note: If your version 19.8 company data includes serious audit errors, you may need assistance from your business partner or consultant to prepare your database for migration.
To migrate your data from version 19.8:
- Click Migrate from Version 19.8 > Migrate Company Data.
- On the Migrate Company Data tab:
- Click [Browse], and then navigate to and select the folder where your version19.8 company data is stored.
Select a company administrator from the list of users that were set up for your company in version19.8.
- Specify a maintenance schedule, including the time and the number of backups to keep.
- Click [Migrate Company].
-
After the migration process has finished, check the SQL Migration Log file, where any errors or changes to your data are recorded.
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.
Converted files are located in shared folders under C:\Sage100Con\Company\[Company Name], organized using a folder structure similar to earlier versions.
After migrating your data
- 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.