Reconciling an acquired platform's admin with the existing product so each side's customers get best of both worlds

Problem

We acquired Roadeazy, an all-in-one video + telematics platform to the portfolio, and the real problem wasn't a missing feature — each platform was strong exactly where the other could be better. The acquired platform carried richer telematics and vehicle-health data; our product carried the deep safety and coaching platform. Customers on either side wanted the whole enriched experience — but you can't just turn on both, because the two systems disagree on identity, org structure, roles, and config (tags vs. a group hierarchy; 4 roles vs. 40+). And the customers who'd benefit most have years of retained data they can't afford to lose or re-enter.

Research

I reframed "integrate the platforms" as an identity- and org-reconciliation problem: cross-platform access and lossless migration are both downstream of one question — do users, vehicles, groups, roles, and config map cleanly across both? The unlock was seeing the two scoping models as role-equivalent — tags and groups do the same three jobs (categorize, scope visibility, drive config), so you map them, not merge them.

Solution

• Reconciled the two admin surfaces — mapped users, roles, vehicles, groups, and config, classifying every setting as shared, unique, or similar-but-different.
• Converged on one model — adopted the existing product's group hierarchy and drove the acquired platform through its APIs, keeping one admin surface.
• Guaranteed continuity — a one-time backfill plus two-way sync carries each fleet's history across, so nobody starts from scratch.
• Unlocked best of both worlds — with identity reconciled, each platform's customers reach the other's capabilities from one login.

Impact

Two half-pictures became one: acquired-platform customers gain the deep safety and coaching stack, and existing customers gain richer telematics, asset tracking, and maintenance data — from a single account, without re-entering years of records. The durable win is the reconciliation pattern: an admin map, a role-equivalence approach, and a backfill-plus-sync continuity model that every future migration and cross-sell plugs into.

Reflection

"Integrate the platforms" was really admin reconciliation — everything valuable was gated on whether identity, roles, and config mapped cleanly across both. Map roles, don't merge shapes. And best-of-both-worlds dies the moment a customer has to start over, so continuity is the precondition for switching.