MPulse-to-MPACT migration needs asset-history reconciliation

Freeze the migration population before counting success

The direct control is a signed population manifest from the source system. Count sites, locations, systems, assets, parent-child relationships, meters, job plans, preventive-maintenance schedules, open requests, work orders by state, labor entries, parts reservations and issues, purchase references, costs, warranties, documents, images, comments, approvals, failure codes, and retained history. Record the extraction cutoff, source version, filters, excluded records, duplicates, missing identifiers, and accountable owners. A completed import job cannot define its own expected population.

Use stable crosswalks for asset, location, worker, vendor, part, account, and work identifiers. Preserve source keys even when the target creates new ones, and record every merge, split, default, truncation, transformation, and rejected record. Effective dates and supersession matter for recurring work: the next due date is not reproducible unless the prior completion, meter basis, interval, tolerance, time zone, and schedule rule also survive. Keep unknown and deliberately excluded records separate.

Reconcile active work and history through one cutoff

Active work needs state-by-state treatment. Decide whether a request, planned job, released order, work in progress, waiting-on-parts item, completed task awaiting review, and cancelled record will move, close, or remain read-only in the old system. Preserve who could act, outstanding permits or isolations, parts and labor commitments, field notes, attachments, approval history, priority changes, and the evidence required for technical completion and restored function. Migration status must not close work or change acceptance.

Historical totals should reconcile by period, site, asset, work type, status, labor hours, material quantity, cost class, and currency where used. Differences need a record-level exception queue with owner, reason, disposition, and retest. Reporting continuity also requires named metric definitions and denominators; a dashboard that looks similar can still change failure counts, backlog age, compliance windows, cost allocation, or availability calculations because the underlying states were mapped differently.

Test cutover, rollback, and retained access

A buyer test should migrate one asset with a parent, meter, recurring plan, open corrective order, reserved part, labor history, attachment, approval, warranty, and corrected completion record. Change the asset hierarchy after the first extract, complete a job during the freeze, create a duplicate part, withdraw a technician's access, and force one rejection. Reconcile both systems, run the next-due calculation, export the exception, and prove the rollback does not create duplicate work or lose a field update.

Maintenance Operations Ledger reviewed MPulse's registered page on September 13, 2026. It supports the current MPACT, migration-path, CMMS, work-order, preventive-maintenance, asset, inventory, reporting, mobile, and integration positioning. It does not disclose a customer's source version, migration tooling, mapping, cutoff, record population, reconciliation result, configuration, adoption, restoration evidence, service level, cost, or outcome. No dated material development after the September 12 cutoff was established.

Enterprise buyer test

Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.

A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.

What we will watch next

Maintenance Operations Ledger will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.