What does Maximo Migration Manager carry, and what must I do after the deploy?

A migration object carries exactly what is in its object structure, and nothing else. Launch points, domain conditions and group members travel in separate migration objects.

Versions: On Maximo Application Suite 9.1 we confirmed, read-only, that the delivered migration object structures carry the same objects as listed here (17 November 2026). We first read them, and made a test package, in our lab on Maximo 7.6.1.0 (3 November 2026). A full deploy needs a second system and was not run on either version. How compiled code is delivered is different on Maximo Application Suite 9.1 (see below).

IBM’s page: IBM’s current Maximo Manage documentation lists post-deployment activities: activating records, updating database statistics, updating database user IDs, editing Start Center queries, and turning off administration mode.

Last checked: 17 November 2026

How it works

Migration objectCarriesDoes NOT carry
DMSCRIPTAutomation scripts and their variablesLaunch points: they are in DMLAUNCHPOINT. Both are in the SCRIPTCFG migration group, scripts first.
DMMAXDOMAINDomains with their values (ALN, numeric, synonym, table, crossover), translations and value conditionsThe conditions themselves: those are DMCONDITION, which must come first.
DMCRONTASKDEFCron task definitions, instances and parameters– (instances come with the definition)
DMMAXOBJECTCFGObjects, attributes, indexes, autonumbers (the pending configuration side)– the deploy itself makes the real tables (below)
DMMAXGROUPSecurity groups, their sites, application rights, GL rights and restrictionsGroup members: users are DMMAXUSER, a separate object.
DMESCALATIONEscalations, points and notificationsActions and communication templates (DMACTION, DMCOMMTEMPLATE: same group, earlier in order).
DMWFPROCESSWorkflow processes with nodes, tasks, assignments, actions, conditions and notifications–
Compiled sourcesThe class, jar or XML files you list in the packageApplying them. On Maximo 7.6 you rebuild, redeploy and restart. On Maximo Application Suite 9.1 this is different (see below).

In the lab, the package carried a script’s full source, its Active flag and its owner, and the source system’s internal ID numbers.

What we read on both systems: a common piece of advice is “run Apply Configuration Changes after the deploy”. On Maximo Application Suite 9.1 and on Maximo 7.6.1 the list of package progress statuses includes a database configuration step, and Maximo has the message “Successfully applied data dictionary changes into database using Database Configuration”. From these we infer that the deploy applies the change itself and that you give it Admin Mode when it asks. We did not run a deploy on either version, so this is an inference, not a test result.

After the deploy

  1. Objects, attributes and indexes: by our reading, applied by the deploy (above; not tested). Give it Admin Mode for structural changes.
  2. Organisations, sites, workflow processes and communication templates: activate them on the target before you deploy the next package (IBM).
  3. Cron task instances arrive with the Active flag and schedule of the source. Check them before Admin Mode goes off, so a production-only task does not start in test (or the reverse).
  4. Scripts arrive Active as on the source. Launch points come only if DMLAUNCHPOINT is in the package. Deploy scripts before launch points.
  5. Security groups: add the options the Security Groups screen would have added for you (“also grants”). Users are not members unless DMMAXUSER is in the package.
  6. Compiled sources: on Maximo 7.6, rebuild, redeploy and restart. On Maximo Application Suite 9.1 this is different: custom Java classes and XML are delivered in a customization archive. IBM’s Customization archive guidelines say: “When the application is redeployed, the customized files override the files that are provided for the deployment.”
  7. Also on IBM’s list: update the database statistics after table or index changes, re-create database user IDs (IBM: “the user data for associated database user IDs is not migrated”), edit the queries of a migrated Start Center template, and turn off administration mode when the deployment finishes.
  8. System properties: live-refresh or restart, as each property needs.

Check what a migration object carries before you trust it

  1. Open Object Structures, filter Consumed By = MIGRATIONMGR, and open the DM… structure.
  2. Read its source objects and relationships. If a child you need is missing, make your own structure (Consumed By MIGRATIONMGR) in your own migration group. Do not change the delivered DM… structures.
  3. In the package definition, set a where clause on each object you use.

Where it breaks

How we checked it

On a Maximo 7.6.1.0 lab system we read the delivered Migration Manager object structures, their processing classes, the Migration Manager properties and messages, all read-only. We then made a test package with a test domain and a test script and read the package content. On Maximo Application Suite 9.1 we read the same delivered structures and messages, read-only, and compared them. Everything we made was given a test marker and removed afterwards; we checked with read-only queries that nothing was left behind.

Not tested: a real deploy, which needs a second system. The after-deploy steps come from the structures, the messages and IBM’s documentation.

This page is part of our Maximo knowledge pages: answers we have checked on a real Maximo system in our lab. For questions about your own Maximo data, see Interpretos for Maximo.