Canzonia · Case Study Report
FILE NO. 04
From Minutes per Click to Instant
A CRM Rescue on Odoo
An established Canadian bullion dealer’s custom CRM had slowed to minutes per click. We moved it onto one fast Odoo system along with its separate transaction database, and migrated and verified the full history.
By the Numbers
page loads, where every click in the legacy CRM once took minutes
lead records migrated, alongside hundreds of thousands of client notes and messages
records lost, with counts reconciled against the source, spot-checked, and signed off by the client
from diagnosis to a working system, the CRM rescue delivered start to finish
The Challenge
An established Canadian precious-metals (bullion) dealer, more than two decades in business, ran its client relationships on a custom-built CRM that had slowed to a crawl. Every click took minutes.
Client-account transactions lived separately in a clunky Microsoft Access database with weak controls, running on an in-house server that had already failed once.
That left critical client data both hard to keep current and exposed.
Note 01
Ten thousand client records, with hundreds of thousands of messages attached. The CRM fetched all of it on every click.
What We Delivered
A performance rescue first, then a second system once the CRM had proven itself in daily use.
DIAGNOSIS
Pagination in the wrong place
The legacy CRM paginated in the browser instead of on the server. Every page view pulled down all 10,000+ records and faked the pagination, so each click loaded everything.
MIGRATION
A history proven, not promised
Migrated over 10,000 lead records and hundreds of thousands of client notes and messages. We reconciled the counts against the source, spot-checked them, and got client sign-off.
SECOND SYSTEM
The Access silo, retired
With the CRM adopted and in heavy use, we rebuilt their stranded transaction database as a dedicated client-account transactions app in the same Odoo system.
The rescue
SERVER-SIDE PAGING
Migrated the CRM onto cloud-hosted Odoo, where proper server-side pagination made navigating the system instant instead of minutes-long
OFF THE IN-HOUSE SERVER
Moved the data off an in-house server that had already failed once, onto cloud hosting the business no longer had to maintain
Rollout & scope
FALLBACK
Left the old systems available as a fallback until the client was ready to switch them off, with no forced cutover date
SCOPE DISCIPLINE
Kept scope to the CRM and transactions: their QuickBooks accounting stayed untouched, deliberately out of scope
The Outcome
What once took minutes per click became instant, with the CRM rescue delivered in a few weeks.
The system was adopted and used extensively from the start.
Over time, client relationships and account transactions came to run from a single cloud-hosted source of truth in Odoo, with the full history intact and verified.
Note 02
Accounting remained on the client’s QuickBooks throughout, deliberately outside the scope of this engagement.
In Closing
A rescue that earned the next project. The stranded transaction database followed within the year.
More Like This
Other Odoo engagements, from a shop floor to a trading desk.
Similar Situation?
If this sounds familiar, say so.
Book a 30-minute intro call. We'll tell you where Odoo fits, and what we'd need to see before we could scope it.
Book a Free Intro Call