Data for Good Calgary — HubSpot to Mautic Migration
Data for Good Calgary
Challenge
A volunteer-run non-profit ran its marketing on HubSpot's free tier. It worked, but it was a ceiling: the next things the chapter needed, such as workflow automation and fuller API access, sat behind paid tiers, and the contact data lived outside the chapter's own cloud. For an organization running on donated time and a minimal budget, growing inside that product meant a cost cliff.
Solution
Inventoried the live account through its API to establish what was genuinely in use, then migrated the marketing-automation function to self-hosted Mautic, the open-source equivalent that covers public forms and CASL-compliant double opt-in without a paid tier. Contacts, custom fields, forms and email templates were migrated with their consent state and lifecycle classification intact, the forms were rebuilt in the chapter's brand, and outbound mail was routed through OCI Email Delivery.
Results
- ✓ No licence cost, now or as the list grows
- ✓ Contact data in the chapter's own OCI tenancy
- ✓ Contacts and consent state migrated without loss
- ✓ Branded public forms embedded in the chapter website
- ✓ CASL compliance kept intact through the move
The brief started as “replace HubSpot” and the first useful thing to do was set it aside. Before choosing a replacement, we pulled an inventory of the live account through its API to find out what the chapter actually used.
The answer was narrow. A small number of public web forms, an occasional newsletter, basic segmentation, and CASL double opt-in. No deals, no tickets, no sales pipeline. The relationship-management half of the platform was empty, because that work already lived in the chapter’s Oracle volunteer platform. What the chapter used HubSpot for was, in practice, a mailing tool, and the features it would need next were the paid ones.
That reframed the decision. An open-source CRM was considered and rejected on a specific point: its free tier cannot do public web forms or native double opt-in, which are precisely the two features in use. Mautic covers both, so it won.
Auditing before migrating
The inventory did more than justify the tool choice. It also surfaced a sync between the chapter’s Oracle platform and the marketing platform that had stopped running some time earlier, so the contact list everyone trusted was out of date.
That was fixed and reconciled before the migration snapshot was taken. Migrating first would have carried the gap into the new system and made it permanent.
Migration
Mautic runs in Docker Compose on OCI compute behind the chapter’s existing load balancer, with a Let’s Encrypt certificate and automated renewal.
| Migrated | Approach |
|---|---|
| Contacts | Moved with source tagging so origin stays traceable |
| Custom fields | Mapped to proper field types rather than dumped as text |
| Public forms | Rebuilt in the chapter’s brand with consent and captcha |
| Email templates | Imported unpublished, so nothing could send accidentally |
| Consent state | Do-not-contact status and lifecycle stage carried across |
Contacts were classified on the way in using the source platform’s own lifecycle data: volunteers, subscribers, and a third group with no recorded legal basis for contact. That last group was explicitly marked do-not-contact until they opt in through a form. That is the cautious reading of CASL, and the right default when there is no evidence of consent.
Every migration script is idempotent and re-runnable, so it was safe to iterate against live data instead of attempting a single irreversible cutover.
Brand and integration
The forms embed into the chapter’s WordPress site at calgary.dataforgood.ca. The chapter palette, typography and wordmark sit inside the form wrapper, so the forms look like part of the site rather than a bolted-on third-party widget.
One class of bug is worth recording, because it is invisible to the people who report it. Forms embedded on the HTTPS site silently failed to load because the platform’s configured base URL was HTTP, so the browser blocked the form script as mixed content. The form rendered as nothing at all, with no error a non-technical user could act on or describe.
Submissions now auto-tag by type, notify the team through branded emails, and land in segments that drive campaigns. Outbound mail goes through OCI Email Delivery with DKIM.
HubSpot’s free CRM was not switched off: it stays in place for contacts and companies, and the volunteer platform pulls and reconciles it every six hours. Mautic took over what the free tier could not grow into: forms, consent and email.
Live at dfgcrm.dataforgood.ca. Part of a three-piece engagement with the volunteer platform and the cloud infrastructure.