Define Migration Project

The Migration Project is the main key for the Data Migration Manager and holds everything together in the Migration Project. In order to start the migration, project basic data should be in place. Users can create a project from scratch or by using the templates provided and can create a template project too, if they wish to use it in other projects. In order to move forward in the migration process Sources, Connected Environments, Main Processes, Sprints, Migration Object Scope, and Target Table Scope should be in place.

Template Migration Project

A Template Migration Project Simplifies the setup work for the new migration project. It holds predefined migration objects, target tables, as well as predefined configurations such as Conversion list, and additional deployment processes for target tables. If a project is tied up with a template project, default definitions, alternative fields, alternative references, user defined fields, object references, additional deployment related information, migration objects, target table scopes, and target file definitions associated with that template will be automatically imported to the migration object scope and target table scope. These templates can be created or imported into the working environment. When a template is loaded, first its data is inserted to the template load area and later data is transferred to the respective locations by reading this location. Exporting and importing template is allowed to perform from the client and server side.

Note:

• Users have the freedom to manipulate the project created from the template project.
• Prior to importing a template project, the migration project header should be defined.

Select and Connect to Template Migration Project

Connect a Template Project that should be used for the Migration Project by selecting it from the dropdown list as seen below:

Create Migration Project Header

A project can be a customer or a template project or can be defined based on a template project. A Migration Project Header defines an ID and name for the migration project. It is also possible to define how the date, number formats should be displayed in the tool.

Exporting/Importing Project & Related Data

The user should be able to perform both export and import operations for all or specific data migration project-related entities/information in a single step.

Project Exporting

In order to export the DMM project, that project should be enabled as 'Template Project' and the user can navigate through Project[Options] -> Export DMM Project, which will open a dialog including export options.

Users can either select default export options that are already enabled or user can enable all the additional options that are used within the scope of the project. Furthermore, the user can export one option at a time and the user will be notified if there are any dependencies between export options while selecting those options.

In the next step, the selected data elements can be exported to a single text file either on the client or on the server. The resulting file will include data elements in a comma separated format.

Note: When exporting mappings, it will not export data rows in the legacy load rather it will export the metadata. This way it ensures when importing the same template, the mapping object is configured and ready to process data.

Project Importing

'Import DMM Project Export File' allows to import of the exported project template file and the data elements that are included in the text file will be imported to the project accordingly.

Note: When importing mappings, if there are already mappings available, those mappings will be replaced with the imported mappings.

Basic Data Validation Options

Validate Basic Data - This entails determining whether to validate the basic data for all target tables within the project. This setting can be established globally.

Basic Data Validation Target - This entails globally configuring the target environment to validate basic data for all target tables within the project.

Note: When enabling "Validate Basic Data" or updating the "Basic Data Validation Target", a confirmation dialog will prompt if there are any environments specified on target table definitions for reference fields. This dialog will request confirmation to clear the specified target environments on those reference fields in the target table definitions.

Target Environments

In Data Migration Manager, Target Environments need to be defined. The target environments are the environments where the data will be deployed. One of these environments will be the same as where the Data Migration Manager is installed and the others will be the Connected Environments.

Installed Environment

As the name itself describes this section will allow a user to specify information regarding the installed environment of the Data Migration Manager. For security reasons, this will be the PROD environment most of the time. The user has the opportunity to control data deployment to the installed environment and data extraction from the installed environment via the Drop downs ' Deployment Status ' and ' Upload Status'.

Connected Environments

Target Environments, outside of the Installed environment, are required to deploy data into or extract data from must be specified under this tab. Database Links to target environments will be created by Cloud Operations in the application and the user can select them from the Drop Down ' Database Link Name ' and configure it accordingly. The Database Links will be created to environments sitting under PROD. There will be no Database Links created to PROD, and that is why it normally should sit in the Installed Environment.

Sources

Sources are used to describe where data originates from. This is usually Legacy Sources, meaning the customer’s current systems. But data can also be extracted from a Target Environment and in this case, the Target is also seen as a Source and will be automatically created as a Source, when data is extracted the first time. Other than the source name and source description, the source priority order must be specified here which is used in the duplication elimination process. Priority order 1 to 9 is reserved for the sources created from the installed and connected environments (with the exact name as the target environment name) specified under the project. In addition to that specifying the date format and number formats (thousand separator and decimal point) should be defined.

Default Definitions

Read more in Extra Configuration

Main Processes

Main processes are optional configuration that helps to organize, track the migration process in Data Migration Manager by specifying the areas and the personnel responsible for the given process.

Sprints

Sprints are optional configuration that divides the migration project into time buckets. The purpose of Sprints is to align the Migration Project with the Implementation Project, so the right data is available for the right area at the right time.

Project Analyzer

The Project Analyzer lists all Target Tables and their statuses regarding the Master Environment. From here the updates can be executed. To get a good overview it is possible to export a summary file or enter the Update Summary Screen.

The first step to Analyzing the environment is to start the scan, which creates a report of differences in the Project Analyzer. Based on the Report, it is possible to take necessary actions to update the Target Tables Definitions when wanted. This way the Migration Project will be able to keep track of added Custom Fields or any other Table change.