DM REVOLVE
Data Migration Toolset
DM REVOLVE is DataMC’s proprietary migration toolset, built to support structured delivery, data quality control, traceability and repeatable execution across every engagement.
Overview
What DM REVOLVE does
In short, DM REVOLVE is DataMC’s ground-breaking proprietary data migration toolset. It is powered by the BIDM methodology and developed over decades by industry experts.
The toolset is used on every engagement and clients get to experience the full use of the tools while working alongside DataMC consultants.
- Proprietary toolset used on every engagement
- Built on BIDM methodology
- Developed by experienced migration specialists
- Supports transparency, accountability and control
Below is a breakdown of the core DM REVOLVE tools.
Core tools
Toolkit Access Portal
TAP is the control hub of DM REVOLVE. It houses the main toolset and provides access to the utilities used throughout the migration process.
WOM
Workflow-O-Matic
POM
Profile-O-Matic
MOM
Map-O-Matic
ROM
Report-O-Matic
TOM
Translate-O-Matic
FOG
File-O-Gen
15-step process
Tracked, managed and signed off end to end
Single control hub
One interface for the full migration lifecycle
TAP
Toolkit Access Portal
The control hub of DM REVOLVE, TAP houses all of our toolsets. From here you can access the tools used throughout a data migration engagement.
- WOM – Workflow-O-Matic
- POM – Profile-O-Matic
- MOM – Map-O-Matic
- ROM – Report-O-Matic
- TOM – Translate-O-Matic
- FOG – File-O-Gen
This is the primary interface for coordinating migration activity, checking progress and moving work through the delivery lifecycle.
Workflow
Workflow-O-Matic (WOM)
WOM is the gatekeeper of DM REVOLVE. Through the WOM interface, every part of the 15-step data migration is tracked, reported on, updated and signed off.
- Tracked
- Reported on
- Updated
- Signed off
For each data object it is easy to see what stage it has reached, whether it is on schedule, the quality of the data, the current status and who is responsible at that time. Problems can be spotted quickly and relevant parties are informed as objects progress through the process.
Selection criteria
Profile-O-Matic (POM)
POM uses the selection criteria from the legacy source to obtain the required data set. This is then used to create the data objects.
- Data source
- Table names
- Object descriptions
- Additional notes
The SQL SELECT statements used to extract data from the legacy sources are recorded here. Once extracted, the data owner checks the result against the expected data set and signs off before the object progresses.
Mapping
Map-O-Matic (MOM)
MOM takes the completed selection criteria and performs the mapping from source system fields to target load template fields.
- Source system data fields
- Target load template fields
This work is performed by the data analyst and subject matter experts from the client. Required translations and data quality checks are identified at this stage, along with the severity of any data quality issues.
Once mapping is complete, the object is submitted for review, approval or refinement. If refinement is needed, it goes through the MOM cycle again.
Reporting
Report-O-Matic (ROM)
The ROM review process shows the results of POM, MOM and coding. It is the verification and data quality step where the number of records and the quality of the objects are checked.
- Selection criteria
- Mapping
- Coding
- Record counts
- Data quality of objects
ROM tracks the quality of the extracted data through a traffic-light system and gives a clear breakdown of any errors, affected fields, exceptions and record-level issues. It should be monitored by the client’s subject matter experts as well as DataMC technical leads, analysts and coders.
Translation
Translate-O-Matic (TOM)
TOM enables client data owners to ensure all translations are completed and correct. This helps improve data quality and supports a smoother migration.
All data translations take place in TOM and are tracked and updated there. If a legacy field needs updating from one value to another, TOM is where it happens. Results can be exported if needed.
TOM is also used for inflight duplication cleansing, including the merging of separate accounts and associated data where required.
File generation
File-O-Gen (FOG)
File-O-Gen generates load files from stored model tables, ready for import into the target system. Once generated, the loads can be tested daily.
- Fast generation of structured files
- Repeatable load creation
- Catching and correcting errors
- Automation and predictability
Next step
See how DM REVOLVE supports migration delivery
If you need a structured, traceable and controlled migration process, DM REVOLVE provides the operational framework to support it.
