The migration from Consuman to Consuman Evolution is carried out through a planned process that allows for the analysis, debugging, transfer, and validation of information before starting to operate in the new system.
During this process, the client and the Consuman team work together, defining beforehand what information can be migrated and what adjustments are necessary before making the change.
Before we begin
To begin the migration process, the following conditions must be met:
- Having confirmed that the current implementation can be migrated to Consumer Evolution.
- Having identified and documented any possible restrictions or functional differences that need to be taken into account.
- Obtain customer confirmation to proceed with the migration.
- Define a responsible party on behalf of the client and a responsible party on behalf of Consuman.
The client representative is primarily involved in decision-making, information cleansing, and validation of migrated data.
The Consuman manager accompanies the process, analyzes the information, proposes migration criteria, and carries out the corresponding technical tasks.
Stages of the migration process
1. Learn about Consumer Evolution
Before starting the migration, introductory documentation on Consumer Evolution is shared.
This material allows you to learn about the main differences with respect to Consuman, the concepts that change and the considerations that must be taken into account during the process.
The goal is to have a prior context before starting the analysis and preparation of the data.
2. Analyze the existing information
An analysis of the current database is performed to determine:
- What information can be migrated.
- What information requires prior cleaning.
- What are the differences between the current structure and Consumer Evolution?
- What alternatives can be applied to correctly transfer the data?
The results of this analysis are used as a basis to define, together with the client, how the migration will be carried out.
3. Define the migration criteria
Based on the analysis carried out, the particularities found are reviewed together with the client and it is agreed how to handle each case.
During this stage, the criteria for cleaning and organizing the data are defined, taking into account the current use of the system and how that information will be used in Consumer Evolution.
4. Refine the information
Before performing the migration, it is necessary to prepare the data that will be transferred.
Debugging may include, for example:
- Information correction.
- Unification or modification of identifiers.
- Review of duplicate records.
- Definition of information that will not be migrated.
- Adjustments needed to adapt the data to the Consuman Evolution structure.
To perform these tasks, a Consuman test environment and a Consuman Evolution test environment are available. The information prepared in the Consuman environment will be used as the basis for the migration.
5. Migrate and validate the data
Once the debugging is complete, a first migration to the Consumer Evolution test environment is performed.
The client must review the migrated information and verify that:
- The data is correct.
- There are no inconsistencies.
- The relationships between the records are as expected.
- The information can be used correctly in the new system.
If any pending adjustments are detected, the necessary corrections are made and the migration is repeated until validation is complete.
6. Train the users
Once the information is validated, training sessions on Consumer Evolution are conducted.
Whenever possible, training is conducted using the client's migrated data, facilitating learning in an environment similar to the one that will be used later.
7. Conduct the final tests
After the training, users perform tests on Consuman Evolution to check the system's operation and familiarize themselves with the new procedures.
During this stage the live release date is also defined.
8. Start trading on Consumer Evolution
On the agreed date, Consumer Evolution will be used as the main operating system.
From that moment on, Consuman ceases to be used for new operations and may remain temporarily available to consult historical information that has not been migrated.