Replace Maximo Facility Management: DACH Compliance Requirements

Your Maximo instance is 15 years old. The consultant who customized it retired in 2019. Nobody remembers why half the workflows exist. You know you need to replace it.

But the compliance manager just reminded you: the next building audit is in 8 months, and the auditor will expect complete maintenance records going back 5 years. Replace Maximo facility management systems wrong, and you hand auditors a gap they cannot ignore.

This guide covers what DACH building compliance codes actually require from your CAFM system, where Maximo replacement projects typically break compliance, and how to migrate without creating audit exposure.

What DACH Building Regulations Require From Your CAFM

German building compliance (Betriebssicherheitsverordnung, EnEV successor GEG, and Landesbauordnungen) and Austrian equivalents (OIB-Richtlinien) require documented evidence of:

Mandatory inspection cycles. Fire safety systems, elevators, electrical installations, pressure equipment. Each has prescribed intervals. Your CAFM must prove inspections happened on schedule, not just that you planned them.

Energy performance documentation. The Gebäudeenergiegesetz (GEG) requires energy performance certificates (Energieausweise) with specific data: heating consumption, cooling consumption, primary energy demand. Your system must store and retrieve these for any building on request.

Contractor qualification records. When a third-party technician services your fire suppression system, you need their certification on file. Not in an email attachment from 2021. In your system, linked to the work order.

Maintenance history with timestamps. Auditors do not accept "we did the maintenance." They accept timestamped records showing who did what, when, on which asset, with which outcome.

The practical translation: any system you use to replace Maximo facility management must maintain unbroken audit trails, support document attachment and retrieval, and preserve historical records through the migration.

Where Maximo Replacement Projects Break Compliance

Most facility teams understand the regulatory requirements. The problem is the migration itself. Here is the typical failure pattern:

Phase 1: Data export chaos. Maximo's data model is complex. Custom fields, linked tables, attachment references. Export scripts miss relationships. You get work orders without their linked assets, or assets without their inspection history.

Phase 2: The spreadsheet bridge. Because the new system's import does not match Maximo's export, someone creates "intermediate" Excel files. Manual mapping. Manual cleanup. Manual upload. Each step introduces errors.

Phase 3: Parallel operation limbo. For 6 months, some technicians use the old system, some use the new one. Compliance documentation exists in both places. Nobody knows which is authoritative.

Phase 4: Audit arrives. The auditor asks for the maintenance history of elevator 3 in Building B. The facilities coordinator searches the new CAFM. Finds records from March onward. Searches the old Maximo. Cannot access it (license expired). Searches the Excel bridge file. Finds partial records with no timestamps.

This is not hypothetical. I have seen this exact sequence at a property management company in Bavaria managing 23 commercial buildings. Their Maximo replacement project took 14 months. The compliance gap cost them a conditional audit finding and 3 months of remediation work.

flowchart TD
    subgraph "Typical Maximo Migration (Manual)"
        A[Maximo Database] -->|"Export script, incomplete"| B[Raw Data Files]
        B -->|"Manual mapping, ~40 hours"| C[Excel Bridge Files]
        C -->|"Manual cleanup, ~20 hours"| D[Formatted Import Files]
        D -->|"Bulk import, errors"| E[New CAFM System]
        
        F[Paper Certificates] -->|"Not included"| G[Filing Cabinet]
        H[Email Attachments] -->|"Not included"| I[Outlook Archive]
        
        E -.->|"Incomplete records"| J[Auditor Request]
        G -.->|"Manual search, ~2 hours per request"| J
        I -.->|"Manual search, ~1 hour per request"| J
    end
    
    style C fill:#ffcccc
    style G fill:#ffcccc
    style I fill:#ffcccc
    style J fill:#ffcccc

The red boxes show where compliance documentation gets lost. The Excel bridge becomes a black hole. Paper certificates and email attachments never make it into the new system at all.

What Compliant Migration Actually Requires

When you replace Maximo facility management systems properly, the migration itself maintains audit trails. Here is what that looks like operationally:

Complete relationship mapping before export. Your migration tool must understand Maximo's data model, including your customizations. Work orders link to assets link to locations link to compliance documents. Export everything or export nothing useful.

Document migration as a first-class concern. Every PDF, every certificate, every contractor qualification letter must migrate with its parent record. Not as a separate batch. With the record it belongs to.

Timestamped migration logs. When an auditor asks "where did this record come from," your answer is a migration log showing: source system, source record ID, migration timestamp, destination record ID. This is your chain of custody.

Validation before cutover. Run compliance queries against the new system before decommissioning Maximo. Can you retrieve the complete maintenance history for every asset class? Can you produce an energy consumption report for any building for any year in your retention period? If no, the migration is not complete.

Single source of truth from day one. No parallel operation period. When you cut over, you cut over completely. Technicians who enter data in the old system create compliance gaps.

flowchart TD
    subgraph "Compliant Maximo Migration (Automated)"
        A[Maximo Database] -->|"Full relationship export"| B[Migration Engine]
        C[Document Repository] -->|"Linked by record ID"| B
        D[Email Archive] -->|"Extracted and linked"| B
        
        B -->|"Validation checks"| E{All Records Complete?}
        E -->|"No"| F[Gap Report]
        F -->|"Manual remediation"| B
        E -->|"Yes"| G[New CAFM System]
        
        G -->|"Complete records, timestamped"| H[Auditor Request]
        
        I[Migration Log] -->|"Chain of custody"| H
    end
    
    style G fill:#ccffcc
    style H fill:#ccffcc
    style I fill:#ccffcc

The green boxes show where compliance documentation is preserved. The migration log provides the audit trail auditors need. The validation step catches gaps before they become findings.

Energy Performance Certificate Requirements

DACH energy regulations deserve special attention. The GEG requires Energieausweise for commercial buildings, with specific data points your CAFM must store:

Primary energy demand (kWh/m²a)
Final energy consumption by carrier (gas, electricity, district heating)
Building envelope characteristics
Certificate validity dates (10 years for demand-based, 10 years for consumption-based)

When you replace Maximo facility management, your migration must preserve this data in a queryable format. Auditors increasingly ask for energy consumption trends, not just current certificates. If your historical data is in Maximo exports that nobody can read, you have a compliance problem.

The ISO 41001 gap analysis we published previously covers how maintenance scheduling intersects with energy efficiency requirements. The short version: your CAFM should correlate maintenance events (HVAC servicing, filter changes, system calibrations) with energy consumption changes. Auditors are starting to ask for this connection.

Contractor Management During Migration

Your Maximo instance contains contractor qualification records. Certifications, insurance documents, training records. When you replace Maximo facility management, these records must migrate with the contractor profiles, not disappear into an archive.

DACH building codes require documented contractor qualifications for safety-critical work. Fire alarm servicing requires CFPA-certified technicians. Elevator maintenance requires TÜV-certified companies. Your CAFM must prove the technician who performed the work held the required certification at the time of the work.

This is where most migrations fail. Contractor records are treated as "administrative data" rather than compliance data. They get migrated last, incompletely, or not at all.

A Nordic facility provider we worked with solved this by treating contractor qualification as a blocking constraint. No work order could close without verified contractor certification. When they migrated, contractor records migrated first, and work orders validated against them before import.

Practical Next Steps

Before you issue an RFP to replace Maximo facility management, run this compliance audit on your current state:

This week:

Export your building list from Maximo. For each building, can you retrieve the current Energieausweis? Note which ones are missing or expired.
Pick 5 assets with mandatory inspection cycles (elevator, fire suppression, electrical main). Can you produce a complete inspection history for each? Note gaps.
List your 10 most active contractors. For each, can you retrieve their current certification documents from Maximo? Note which are missing, expired, or stored outside the system.
Calculate your compliance documentation debt. Missing certificates × average remediation time (typically 2-4 hours per document) = hours before you can migrate safely.

Before vendor selection:

Run the same queries against each candidate system's demo environment. Ask the vendor: "Show me how you would migrate this specific record with its linked documents." If they cannot demonstrate it, they have not done it.

The goal is not a perfect Maximo replacement. The goal is a migration that does not create compliance exposure. The regulatory requirements are clear. The challenge is operational execution.

Need a compliance-focused assessment of your Maximo migration options? Contact us for a 30-minute review of your current compliance documentation state and migration risk areas.