Plan a Maximo move on cited evidence.

Pick where you are and where you are going. The move page composes what IBM says about the move, what breaks, the landmines, what you gain and the plan — every item with its IBM page or published record beside it, and the whole page exportable as an Excel workbook, a PDF or Markdown.

Moves to the current release

Every other pair in the catalogue (7.6.1, 8.11, 9.0, 9.1, 9.2) has its own page at /upgrade/<from>/<to>, with a phased checklist at /checklist, the fixes gained at /fixes and the security catch-up at /security.

On classic Maximo? 7.6.1 here means the whole 7.6.1.x line, so pick it whether you are on 7.6.1.1, 7.6.1.2 or 7.6.1.3. IBM lets you move to Maximo Manage from Maximo Asset Management 7.6.0.10, 7.6.1.2 or 7.6.1.3 only, and from IBM Control Desk 7.6.1.5 with Maximo Asset Management 7.6.1.3 for Maximo IT, so getting to one of those levels is the first item on the plan. The checklist states it with IBM's own sentence.

The desk

Deadlines — end of support and Extended Support dates, each with its IBM source and days remaining.
Deprecation register — what was deprecated, removed or renamed, in which version, and what IBM says replaces it.
Readiness assessment — twelve questions about your system pick out the checklist items that apply; answers stay in your browser.
Paths by industry — every release-to-release move, for every industry Maximo runs in.
Compare versions — deprecations, behaviour changes and gotchas between any two releases.
Change log and Change Watch — what changed across Maximo 9.x, dated and cited, and the curated material changes with Assetize's interpretation.
Maximo Mobile desk — what IBM says about Maximo Mobile, release by release.

How the desk is built

Nothing on a move page is generated on the spot. The route and what IBM says come from IBM's own documentation and support pages, each statement carrying IBM's verbatim sentence, the page it is on and the date it was read. Breaks come from the reviewed comparison archive and the 9.x change log; landmines from the gotcha library and Change Watch; dates from the lifecycle table; the checklist from templates resolved against the published corpus on every request. The same data answers the Upgrade Desk tools on the MCP server: upgrade_plan, upgrade_checklist, fixes_gained, deprecation_register and lifecycle_dates.