Database vendor conversion
Move your Maximo database from any of MSSQL, DB2 or Oracle to any of MSSQL, DB2 or Oracle.
End-to-end conversion of a Maximo database between Microsoft SQL Server, IBM DB2 and Oracle, in any direction and any combination. Done with a tested approach that preserves data, customisation, integrations and historical attachments, with a controlled cutover and a rollback plan.
Database conversion is one of the riskiest things you can do to a Maximo estate. It is also one of the most valuable, when the rest of the corporate database strategy demands it. The risk is in the approach, not the operation: dry runs, validation, customisation handling, rollback. Done with discipline, it is routine. Done without, it is a long weekend nobody wants.
What we deliver
- Assessment of source and target databases, customisations, integrations and constraints
- Repeatable conversion process with multiple dry runs before any production change
- Data, customisation, integrations and historical attachments preserved end-to-end
- Vendor-specific SQL identified, refactored and tested before cutover
- Controlled cutover window with a tested rollback plan
- Reconciliation report after cutover, signed off before the change is closed
How it fits with the rest of the programme
Database conversion is often combined with Maximo to MAS upgrade or with a move to MaxIron managed hosting. It pairs naturally with data migration work where reference data and integrations are also being reshaped. On large estates running multiple environments, the conversion uses Cloud Manager to coordinate environments and Change Control to gate the cutover.
Sectors we have done conversions in
Related capabilities
Related capabilities you might also need
MaxIron products
MaxIron products that make a database conversion safer to land
Database vendor conversion — frequently asked questions
- Which database conversions do you support?
- All combinations between Microsoft SQL Server, IBM DB2 and Oracle, in any direction. Most commonly we are asked to move from one of those to another to consolidate a corporate standard, escape a vendor, or align with a target hosting model.
- Is this safe for a production Maximo estate?
- Yes, when done with the right approach. We preserve data, customisation, integrations and historical attachments, run multiple dry runs, validate row counts and checksums, and have a controlled cutover with a rollback plan in place. This is not a one-night cowboy job.
- What about customisations and Automation Scripts?
- Maximo customisations and Automation Scripts are preserved through the conversion. Where the source database has vendor-specific extensions in custom SQL, we identify and fix those before cutover so nothing breaks on the new platform.
- Can this be combined with an MAS upgrade?
- Yes, and it often is. Database conversion plus Maximo to MAS upgrade is one of the cleanest ways to land an estate on a sensible long-term platform.
- How long does a conversion take?
- Typical cutover windows are measured in hours, with the bulk of the work happening in dry runs beforehand. Total programme length depends on the size of the database and the depth of customisation, and we give a fixed estimate after an assessment.
Move databases without the weekend everyone dreads.
Tell us your source and target database vendors and the rough size of the estate. We will scope a conversion plan with dry runs, cutover and rollback.
Scope a database conversion