Planning for the Migration

Before you begin importing data, ensure that you have performed these planning tasks:

• Determine where to place the external application and migration databases.

  Data will be migrated from the external application database into an CloudSuite Industrial migration database. These databases can exist on the same SQL server or they can reside on different servers. After the migration is complete, you can copy the target table data from the migration database into an CloudSuite Industrial production database.

• Determine what data is required in CloudSuite Industrial.

  Use a spreadsheet to list the forms in CloudSuite Industrial where data must be entered, and, where possible, the CloudSuite Industrial tables underlying those forms. If your external application has a matching table whose data can be mapped to an CloudSuite Industrial table, specify the external table name in the spreadsheet.

  List the CloudSuite Industrial forms in sequential order in the spreadsheet. The sequence indicates the order that the data must be specified because of data dependencies. For example, you must generate lists of certain codes before you can use those codes in master data such as a Customers form.

  Note:  This spreadsheet might already be available for your external application; check with your Infor consultant.
• Compare external application data to CloudSuite Industrial data.
  Note:  For the Infor VISUAL migration, a sample set of mappings, transformations and rules has been predefined.

  Compare the CloudSuite Industrial table schema (column names, data types, and valid values) to your external application table schema:

  • Use the CloudSuite Industrial Database Schema Report (generated through a form in the application) and the CloudSuite Industrial DataMap Schema-Properties spreadsheet (available on the Infor Support Portal site) to see the columns and data types for each table, so that you understand the CloudSuite Industrial schema.
  • For areas where your table data can be mapped to CloudSuite Industrial tables, determine the transformations (changes to data types, length, etc.)  that are required. Later, you can use the Preliminary Data Transfer process to help you determine other required transformation rules.
  • For areas where CloudSuite Industrial requires initial data, but the external application does not provide it, you can enter the data manually in the forms. Where possible, you can generate spreadsheets from CloudSuite Industrial form grids, using the Export to Excel option. Fill in your data and then paste the updated spreadsheet data back into the form. See the CloudSuite Industrial online help for information about pasting into forms from a spreadsheet.

  You are not required to use the migration utility to import data into CloudSuite Industrial tables. You can manually load data into a CloudSuite Industrial table if you want to create new records that are not dependent on the existing data in the external application.

• Determine the migration sequence.

  CloudSuite Industrial data must be loaded in a certain order. Some data is dependent on the existence of other data. See the sequences on the Import Steps form. These sequences were tested with a sample database.

  See each mapped target table's dependencies and then set up the import sequence for the mapping tables based on those dependencies. If there is any prerequisite data that must be manually loaded into the target table (because the prerequisite data does not exist in any source table), ensure that the prerequisite data is loaded before you import the source table's data.

• Prepare the external application data before the migration.

  In the external application, you must perform steps to complete and post all transactions before the migration, to ensure that CloudSuite Industrial has the most up-to-date information and that no transactions are missed. For example, post all unposted invoices, vouchers, journals, and job transactions, and print and post A/P and payroll checks.

  After these steps are performed, no new transactions should be created in the external application. Any new transactions should be created in CloudSuite Industrial after the migration is completed.

• Define the future storage environment.

  Determine the SQL Server and CloudSuite Industrial production database/site where the transformed migrated data will reside.

• Develop the pre- and post-migration verification plan.

  A detailed verification plan must be prepared before you proceed with the data migration. This plan should be shared with members of other departments that will use the data.

  Documenting your migration process can help you train your staff and simplify or streamline the next migration you perform, reducing both expense and risk.

  After the data is successfully transferred into the CloudSuite Industrial database, have a plan in place to verify that all of the data was correctly transferred. If some data did not  transfer as you expected, analyze the mapping and related functions that were performed in database triggers. Determine any additional configuration or processes that must be performed to complete the migration.

  When the data transfer is verified, perform a backup of the existing database.