Written from migrations and operations work our consultants have actually delivered — what we sequenced, what we rebuilt, and the parts that cost more than anyone quoted for.
A marketing automation migration breaks at the logic layer, not the data layer. Contacts, assets and activity history move without much drama — the vendor will do most of that for you. What has to be rebuilt is everything that made those records mean something: scoring, lifecycle, operational programs, sync behaviour. Treat the project as a file transfer and you go dark mid-quarter.
Read it →An Eloqua to Marketo migration is two projects sharing one name: moving assets and programs across, and moving the website's data collection across without losing a submission. The second is the one that gets under-scoped. Eloqua's Campaign Canvas and Marketo's Smart Campaign model do not map one to one, so budget for rebuilding logic rather than translating it.
Read it →A Pardot to Marketo migration gets harder the moment there is more than one Pardot instance to move. Consolidating several instances into one Marketo instance is a design problem before it is a migration: a workspace and a person partition per acquired organisation, a subdomain each, a decision about which instance goes first, and a Salesforce connector that can only serve one arrangement at a time.
Read it →Marketing automation consolidation after acquisition works best when the acquired brands stay separated inside one instance rather than blended on day one. Workspaces hold each org's assets and programs. Person partitions hold each org's database, and every org keeps its own sending and landing page subdomains. Consolidate the platform and the licence first. Leave the brands alone until someone senior decides to retire one.
Read it →A HubSpot to Pardot migration is mostly an automation rebuild. Emails and landing pages are an HTML and CSS job and everyone worries about them first; the operational programs are the actual work. Pardot has no equivalent of a HubSpot workflow, so one workflow becomes some mix of automation rule, completion action, dynamic list and Engagement Studio program. Lifecycle and scoring get redesigned, not copied.
Read it →A HubSpot to Odoo migration is mostly a learning project wearing a migration project's clothes. Odoo has no like-for-like equivalent of HubSpot's workflow editor or its smart lists, so program logic gets rebuilt rather than ported — much of ours ended up as regular expressions in server actions — and someone has to learn the platform well enough to teach it. Price the learning, not the export.
Read it →If you are scoping a move between platforms, or halfway through one that has stalled, a free 30-minute call will tell you which of the above you are about to hit.