7.6 to MAS Migration

• A dated, deadline-anchored migration roadmap (7.6 base support ended 30 September 2025, so you are already past due, and we treat it that way)
• A right-sized AppPoints plan and an OpenShift platform your team can actually operate, on the topology you choose
• A low-downtime cutover with your customizations and integrations carried forward, not lost, and a clean hand-off into run-and-maintain
• A migration run as a data-operations discipline: validated, repeatable, audited, because upgrades fail on the data, not the platform

How it works

Maximo 7.6 base support ended on 30 September 2025. The last interim fix for the 7.6.1.x line shipped that same day, and IBM's only stated path forward is to trade up to the Maximo Application Suite. If you are still on 7.6, the clock is not ticking; it has already run out. We start from that fact and work backwards to a plan.

A real 7.6-to-MAS migration is five jobs at once: a data and version upgrade into MAS Manage, a new platform (Red Hat OpenShift) most 7.6 shops have never run, a new licensing currency (AppPoints), years of customizations and integrations to carry forward, and a Continuous Delivery operating model to adopt. No single in-house team usually owns all five. That gap is the work.

We run it as one fixed-scope program through our D2D Line:

1. FRAME — a readiness assessment pins your environment, your AppPoints exposure, your OpenShift readiness, and what "done" means, in writing.
2. DESIGN — we design the target topology and the cutover, and you sign off before anything moves.
3. PLAN — the migration becomes a sequenced, testable plan with a rehearsed cutover window.
4. BUILD — we upgrade the database, stand up the platform, and carry forward the customizations that earn their keep.
5. VERIFY — we prove source-to-target data parity and that the suite behaves, before you go live.
6. SHIP — we cut over in a tight window and hand you a clean, documented MAS estate.

What you own at the end

A clean, documented MAS Manage estate on a platform your team understands, with a right-sized AppPoints plan and the customizations that survived the cut written down. No black box, no runtime that ties you to us. The migration artifacts, the data pipeline, and the cutover runbook are yours.

The four leaf offerings below are the stages you can buy individually or as the full program: the readiness assessment, the upgrade and OpenShift re-platform, the customization and integration carry-forward, and the managed cutover.

FAQ

We missed the September 2025 deadline. What now? You have two honest options, and both end in MAS: migrate now, or buy IBM Extended or Sustained Support as a bridge while you plan the move (which requires showing an upgrade roadmap). We can run either, and the readiness assessment tells you which is the sane call for your situation. The 7.6 Extended-Support Bridge lives under Managed Maximo for exactly that reason.

Is this a rip-and-replace? No. The migration to MAS Manage is a data and version upgrade of your existing Maximo database, re-platformed onto OpenShift. Your asset and work-management data model carries forward; the schema lineage is continuous. What changes underneath is the platform, the licensing, and the operating model.

How is it priced? Fixed-scope, fixed-fee, staged. The readiness assessment is the free entry point; each stage after it is scoped and priced before it starts, so you never sign a blank cheque for an open-ended project.

• Migrations delivered to a single-digit-hour cutover window with zero data loss
• Years of legacy customizations assessed item by item: carried forward where they earn their keep, retired where they do not