IBM Maximo Data Loading Tools (MAS 9): a Comparison
Updated on · VAGANET EAM
In short. Every serious tool goes through Maximo's official interfaces (REST API or MIF), never through the database. They differ by ground: MxLoader for the desktop and Excel, MIF for recurring feeds, the REST API for custom work, Migration Manager for configuration only, third-party ETL for syncing systems, and MAS9 for multi-environment migrations you must prove.
An IBM Maximo Manage (MAS 9) data init or migration almost always starts with the same question: what do we load with? This comparison covers the real options, what they do well and where they stop. It is written by the team behind MAS9; we have tried to stay factual about the other tools.
The criteria that matter on a project
- Business logic: does the load go through Maximo rules (validation, statuses, counters)?
- Volume: a few hundred rows or several hundred thousand?
- Environments: DEV, UAT, PROD, each with its own configuration.
- Resume: what happens after a network drop or a run of rejections?
- Checks and proof: do you know before sending what will be rejected, and can you prove afterwards that every row arrived?
- Teamwork: central log, permissions, API keys kept off workstations.
Comparison table
| Tool | Type | Strength | Main limit |
|---|---|---|---|
| MxLoader | Free community Excel workbook | Known by everyone, read and write in one tool | Runs on a workstation: large volumes, resume and multiple environments handled by hand |
| MIF (enterprise services, flat files) | Native Maximo | Recurring feeds, queues, reprocessing of failed messages | Per-environment setup (external systems, services), hard-to-read error tracking |
REST API (/maximo/api/os) | Native Maximo | Full flexibility, upsert, bulk calls | Everything must be built: resume, log, checks, read-back |
| Migration Manager | Native Maximo | Moving configuration between environments | Does not load business data (assets, locations, items…) |
| Third-party ETL (for example Cohesive Data Utility) | Commercial product | Synchronization and migration between systems, per the vendor | Dedicated installation and licence, sized for continuous integration rather than one-off loads |
| MAS9 | Online service (VAGANET EAM) | Pre-load validation against each environment, resume without duplicates, read-back from Maximo, MxLoader files accepted | Dedicated to Maximo Manage 9.x; paid subscription after the trial |
MxLoader: the desktop tool
MxLoader is a free macro-enabled Excel workbook created by Bruno Portaluri. Each sheet describes an object structure, an action and columns. On MAS 9 you need a recent version (8.x) that speaks the REST API: 6.x versions do not. It is unbeatable for extracting a table, fixing it and sending it back. Its limits show when loading becomes a project: a workstation that must stay connected for hours, rows already sent to identify after an interruption, one workbook per environment.
IBM has also documented a version of MxLoader to deploy in Red Hat OpenShift, as a separate project (container) next to MAS. IBM Champions refer to it on the IBM Community as the IBM-provided variant, useful when Excel is not an option on the workstation. Like the community workbook, it goes through Maximo object structures, which validate every row; it does however require administrative access to the OpenShift cluster, which is rarely available on MAS SaaS.
MIF and REST API: the native interfaces
MIF (Maximo Integration Framework) processes flat or XML files through enterprise services, with queues and reprocessing of failed messages. It suits recurring feeds, provided external systems and services are configured on each environment. The REST API exposes the same object structures over HTTP with an API key: it is the most flexible building block, but everything around the call (resume, log, checks, read-back) is yours to write. On MAS 9 both require the user to be authorized on each object structure: see the BMXAA9301E error.
Migration Manager: configuration, not data
Migration Manager packages configuration items (domains, applications, object structures, conditions, security groups) to move them from DEV to UAT and then PROD. It is essential to keep environments aligned, which in turn conditions successful loads. It does not replace a business data loading tool.
Third-party ETL
Some vendors offer Maximo-specialized ETL toolkits. Cohesive Solutions, for example, presents its Cohesive Data Utility as a synchronization and migration tool between systems, compatible with MAS. These products mainly target platform migrations and continuous synchronization; check installation, licensing and support for your Manage version.
MAS9: industrialized data migration
MAS9 is an online service dedicated to loading Maximo Manage 9.x. It accepts MxLoader workbooks, CSV files and Maximo flat files, then:
- checks each file against the target environment's configuration before sending anything;
- loads through the REST API or an enterprise service, and resumes without duplicates after an interruption;
- reads Maximo back to prove every row arrived;
- reaches Maximo directly, through a relay agent inside your VPN or through a local runner;
- handles several environments and a portal where your clients submit their loading requests.
It replaces neither Migration Manager for configuration nor an ETL for permanent synchronization between two systems.
Which tool should you choose?
| Your situation | Suitable tool |
|---|---|
| Fix a few hundred rows from Excel | MxLoader |
| Recurring feed from another system | MIF, or an ETL if the sync is continuous |
| Very specific need, development team available | REST API |
| Align DEV, UAT and PROD configuration | Migration Manager |
| Large data init or migration, several environments, cutover to prove | MAS9 (MxLoader files reused) |
For the full method, see the IBM Maximo data migration guide and the quality control guide.
Frequently asked questions
What is the best tool to load data into Maximo MAS 9?
There is no single tool. MxLoader suits one-off loads from Excel, MIF suits recurring feeds and flat files, the REST API suits custom scripts. For a data migration across several environments with a cutover to secure, an industrialized tool such as MAS9 adds pre-load validation, resume after interruption and proof of arrival.
Can Migration Manager migrate business data?
No. IBM Migration Manager moves configuration (domains, applications, object structures, conditions…) between environments. Business data such as assets, locations or items is loaded through MIF, the REST API or a loading tool.
Does MAS9 replace MxLoader?
MAS9 takes MxLoader workbooks as they are and loads them server side, with pre-load checks, resume without duplicates and read-back. MxLoader remains handy for a quick extract or fix from Excel: the two tools complement each other.
Can you load directly into the Maximo database?
It is discouraged and impossible on MAS SaaS. A SQL load bypasses Maximo business rules, counters, statuses and audit. Tools that go through the API or MIF apply Maximo business logic.
Load your Maximo data without silent errors
MAS9 checks your files against each environment's configuration, resumes an interrupted load without duplicates, then reads Maximo back to prove every row arrived.
Discover MAS9