Maple Logistics moves 84 million packages per year across nine Canadian provinces. Until late 2024, each provincial office ran its own CRM, its own customer database, and — increasingly — its own definition of what "Maple" meant to a customer.
The problem
Eleven provincial offices on three different CRM systems. A multi-province customer (think a national retailer like Lululemon shipping out of warehouses in BC, Ontario and Quebec) might have eleven account managers, none of whom knew the others existed. A renewal in Montreal had no visibility from the Vancouver office handling onboarding. Compliance was a constant fire-drill because PIPEDA and Quebec's Law 25 have meaningfully different consent requirements.
One of our larger customers had eleven Maple account managers. None of them knew the others existed.
Why they switched
The CIO, Sarah Tremblay, ran a six-month vendor evaluation in mid-2024 — Salesforce, NetSuite, Microsoft Dynamics, and Tracket. Tracket won on three things: data residency in a Canadian-only region (Toronto and Montreal data centres), out-of-the-box CRA compliance for Books, and willingness to ship a custom EDI integration with their carrier-management system within 90 days.
The migration
Tracket's Enterprise migration team scoped a six-month parallel rollout. Each provincial office cut over to a regional Tracket instance, all backed by a single Atlas graph. Canadian data stays in Canadian regions; the graph crosses provinces only on aggregation queries with auditable proxies. Quebec workspace defaults to French; Atlantic Canada opted for English-default with French fallback.
The result
Eleven systems became one. 1.4 million customer records collapsed to 940,000 canonical entities — the rest were duplicates. 99.99% uptime maintained across the 26-week cutover. The first cross-province renewal closed by a coordinated team in week 28.
The first cross-province renewal closed by a coordinated team. That was the moment I knew it had worked.
— SARAH TREMBLAY · CIO · MAPLE LOGISTICS