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
| Migration object | Carries | Does NOT carry |
|---|---|---|
| DMSCRIPT | Automation scripts and their variables | Launch points: they are in DMLAUNCHPOINT. Both are in the SCRIPTCFG migration group, scripts first. |
| DMMAXDOMAIN | Domains with their values (ALN, numeric, synonym, table, crossover), translations and value conditions | The conditions themselves: those are DMCONDITION, which must come first. |
| DMCRONTASKDEF | Cron task definitions, instances and parameters | – (instances come with the definition) |
| DMMAXOBJECTCFG | Objects, attributes, indexes, autonumbers (the pending configuration side) | – the deploy itself makes the real tables (below) |
| DMMAXGROUP | Security groups, their sites, application rights, GL rights and restrictions | Group members: users are DMMAXUSER, a separate object. |
| DMESCALATION | Escalations, points and notifications | Actions and communication templates (DMACTION, DMCOMMTEMPLATE: same group, earlier in order). |
| DMWFPROCESS | Workflow processes with nodes, tasks, assignments, actions, conditions and notifications | – |
| Compiled sources | The class, jar or XML files you list in the package | Applying 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.
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.