You made an excellent choice and selected TRIRIGA/MAXIMO.  As you progress through the Implementation plan, you now face the data Migration dilemma:  what data is necessary for managing your work flow and what data needs to be preserved for reporting?

Data migration is the process of transferring data from one system to another while changing the storage, database or application. Data migration is necessary but storing data into the new system takes significant time and effort.  ValuD recommends only migrating the data which is required to support how you work going forward.  Clients should carefully consider how to manage historical data to avoid taxing the server and affecting the performance of the system.

Before migrating Legacy data, companies must establish a process requiring users to review and delete data that’s no longer needed. Whether structured or unstructured, data takes up space. Organizations should consider how often the data is used, how data is secured, what regulations influence how data is stored and whether the data is vital for business operations. Some historical data needs to be migrated to get the exact fields and tables for reporting and to aid in user adoption.

ValuD has supported over 180 projects and understands the drawbacks of data migration decisions.  Consider the potential impacts for your projects:

1. Historical data takes time and increases system turnaround time.

Example: A telecommunication company migrated their legacy data that required three delta loads. Delta loads are required to make incremental changes to the data.  In contrast, a financial company elected to migrate limited legacy data which eliminated the need for a delta load and saved time and money.

2. Large data migrations require robust hardware and additional set up and maintenance which can get expensive.

Example: A telecommunication company migrated their legacy data that required four application servers and four processing servers with 64 core databases. A financial company who didn’t migrate their legacy data only needed one application server and one processing server with 32 core database, saving hardware costs, implementation time and staff effort.

3. Getting all your data migrated to a new system is called a ‘deep copy’ where all the transactions between the database tables are tracked and maintained which prolongs implementation and negatively impacts system performance.

Example: An insurance organization wanted to copy all its legacy financial transactions.  Migrating that volume of data negatively impacted system operations and performance time.

4. There are few tables available in the database which track each and every transaction in detail. When legacy data is migrated, tables tend to get flooded with historical data, and system will perform poorly.

Example: when there is communication in between two processes of an application, the communication and impact of each other is tracked and recorded.

Data migration is a routine when adapting a new system but not all data needs to be migrated. The client should migrate only the required data to support their process and for reporting. To learn more about best practices or to discuss an implementation of your TRIRIGA or Maximo application, please contact us at [email protected].

The post TRIRIGA/MAXIMO implementation: The Data Migration Dilemma appeared first on ValuD Consulting.