7350 E Progress Pl Greenwood Village, Colorado - 80111. USA
Call Us Today: 602-332-9633

Methodology

Customer Specific Setting

  • Create Resources that will deliver the data migration project.
  • Create the Project Plan from the templates for the source and target applications.
  • Identify tasks and assign them to the resource calendar.
  • Create the data model and data elements that will hold the master data elements for the source and target application.

Import master data file

Import all data sets of the master data file from the database server into the CDM360’s staging area.

Profile master data

Next, profile the imported file.
Profiling provides the organization with detailed information related to the master data file columns. Column names, duplicate column, data type, count of min and max values, count of mixed case values, count of special characters present in the columns. Count of the case the data was stored.

Business users review

Next, the business users review the profiled data on the Web UI interface of CDM360’s business user’s workbench.
A separate task is created on the calendar of the business user to review the profiled master data, and he is required to enter his requirements, identify issues and gaps for each column.

Cleanse

Next, the system administrator will begin the cleanse/standardize process based on the business user’s requirements and recommendations captured in the previous process.

Golden records

Next, the system administrator will begin the de-duplication process to determine the golden records.

Choose from the columns created when the master data file was imported to create the golden record master data file.

The process will create the source master data file with the unique and duplicate count.

Next, the file is exported to the Business user’s workbench for the business to review unique master records and its duplicates.

Preview current state

Next, the business users review the current state master data and physical data model displayed on the Web UI interface of CDM360’s business user’s workbench.

A separate task is created on the calendar of the business user to review the master data file, and he is required to enter his requirements, identify issues and gaps he finds in the master data file.

The current state workbench displays master data records that have duplicate records. The business user can select master data records to use as test data that can be used in further testing by the QA team.

Physical data model

Next, the business users create the physical data model using the business user’s workbench. Here the future state physical data model is mapped to the current state physical data model. This mapping enables the business to be able to trace the legacy master data column and its value to the future state master data column and its value.

A separate task is created on the calendar of the business user to map the future state physical data model with the current state physical data model. During the mapping process, the business users can preview the physical data model with the actual data on the Web UI.

Preview future state

Next, once the mapping process is complete, the business users can preview the future state master data file on the Web UI interface of CDM360’s business user’s workbench.

A separate task is created on the calendar of the business user to review the future state master data file, and he is required to enter his requirements, identify issues and gaps that he finds in the future state master data file.

QA process

Next, once the future state master data file is complete, the QA team can test the future state master data file on the Web UI interface of Cloud migration 360.

A separate task is created on the calendar of the QA user to review the future state master data file with the test data and is required to identify issues and gaps that he finds in the future state master data file. QA team can approve the future state master data file or recommend to repeat the data migration with either the cleansed source master data file to create the future state master data file that will remove issues identified earlier.

Deployment

Next, the future state master data file is ready for deployment to the new modern target MDM or ERP application.