In this section we will cover the migration of data from previous versions of SunSystems. The tasks detailed are those normally expected of an application consultant.

Discuss in forum
Before migrating data, ensure that you have decided and planned how you want to set up your Business Unit and analysis of data in SunSystems 5. Also, ensure that you have read the appendices for more details on how data is migrated from 4.2 tables or files into the SunSystems 5 tables.
Note: The databases created in 4.2 versions, using the function DB=Database Definition, are now referred to as Business Units in SunSystems 5. The Journal Hold File should be empty before you start migrating data and a new Balance File is created in SunSystems 5.1. You should also create a Business Unit and Business Unit Setup record for every Database Definition record in version 4.2.

As soon as you start migrating a Business Unit, referential integrity is automatically switched off.
You are required to switch referential integrity back on at the end of the migration process. You can only migrate one Business Unit at a time. The process described in the following subsections therefore needs to be repeated for each of your existing 4.2 databases.

Stage 1: Backing Up SunSystems 4.2 Data
1. You need to be logged in as an English operator to backup your data. See the Migrating 4.2 non-English database section. Log in to SunSystems, go to OD=Operator Definition and check that the Operator Language field for the Operator Code you use to back up your data is set to 01 (English). Log in to SunSystems 4.2 with this Operator Code and use the function FB=File Backup/Restore to back up your data files.
2. Leave the Database Code field blank and back up your Installation File.
3. Enter the Database Code of the database you want to migrate to SunSystems 5 and then back up the Reference File, the Ledger File, Budget File(s) and Archive File(s).
4. Place a copy or your backup files into your SunSystems 5 backup directory.
The default backup directory is called _back. However, you can specify an alternative location for your backup files using  Operator Setup (OS). Amend the Operator Setup for the operator carrying out the migration and enter an alternative path in the Operator Work Drive field. The path name you enter as the Operator Work Drive must be no longer than 10 characters in length and the path name must end in a backslash. The path must not contain embedded spaces.
For example, e:\temp\ is a valid path; e:\temp, or e:\Temp A\, are not valid.
All backups, including PARAM and PAY files, must be in the same location. If they are not, an Open File error message is displayed when you run Data Migration. Mapped drives included in the path name must be mapped to a location on your hard drive.
You can amend the operator work drive to another location after completion of Data Migration, if required.
Refer to your SunSystems 4.2 documentation for further details on backing up 4.2 data.