Pardot to HubSpot Migration: Start With the Problem

If you are thinking about moving from Pardot, now called Marketing Cloud Account Engagement, to HubSpot, do not start with the migration. Start with the business problem you are trying to solve. Once that is clear, the platform decision, the migration scope and the Salesforce integration all become far easier to get right.

Nobody wakes up excited to migrate a marketing automation platform.

Normally, the conversation starts after someone asks why a fairly ordinary campaign has taken three weeks to launch, why the attribution report needs its own spreadsheet, or why nobody wants to touch an automation built by someone who left two years ago.

That is when Pardot starts getting blamed. Sometimes fairly. Sometimes not.

The real question is not whether HubSpot has a nicer interface or a longer feature list. It is whether your current setup still supports the way your marketing and sales teams need to work, without every campaign becoming a small IT project.

When even straightforward changes require specialist support, multiple approvals or time from already-stretched teams, progress naturally slows down. It is rarely anyone’s fault. It is usually the result of a system and process that have become more complicated as the business has grown.

Over time, that complexity can leave Marketing frustrated, technical teams overwhelmed and good campaign ideas stuck waiting in a queue.

Start with the problem, not the platform

Before comparing software, get painfully clear on what is actually going wrong today. Otherwise, you risk spending a lot of time and money moving the same processes, the same data and the same confusion into a shinier system.

I would start with a few simple questions.

• Are campaigns slow because of Pardot, or because nobody agrees on the process?

• Does Marketing rely on Salesforce specialists for routine changes?

• Can leadership connect marketing activity to pipeline and revenue without manual reconciliation?

• Do Sales and Marketing use the same lifecycle definitions?

• Is the team paying for extra tools to work around gaps in the current setup?

• Is the renewal prompting a genuine platform review, or just a last-minute pricing conversation?

Those answers will tell you far more than a feature comparison ever will. A platform move should solve a business problem. If the problem is not clear, the project is already starting on shaky ground.

Seven signs it may be time to review Pardot

These are the patterns I see most often when a team is ready to review Pardot. One or two on their own are manageable. Four or five together usually mean the platform, the process or the ownership model needs a proper look.

1. Simple campaigns need specialist support

Marketing owns the campaign target but needs technical or Salesforce help to make routine changes. That slows delivery and creates a queue around a handful of people.

2. Reporting is difficult to trust

Attribution requires spreadsheets, manual matching or several versions of the truth before anyone is comfortable sharing the number.

3. Nobody wants to touch the old automation

There are years of rules, lists and dependencies, but very little documentation. Everyone knows something might break. Nobody is entirely sure what.

4. Pardot and Salesforce no longer reflect the same process

Lifecycle stages, lead statuses, routing and ownership have drifted apart. Marketing thinks a lead was handed over. Sales has a slightly different version of events.

5. The technology stack keeps growing

New tools have been added for landing pages, reporting, content, enrichment or automation because the core setup is not meeting the team’s needs.

6. The team cannot explain the value at renewal

The conversation focuses on licence cost because nobody can confidently show the time saved, pipeline influenced, or operational value created.

7. Marketing cannot move at the speed the business expects

The team has the ideas and targets, but the platform, process or ownership model makes execution unnecessarily slow.

Should you migrate everything from Pardot to HubSpot?

No. One of the easiest ways to make a migration unnecessarily expensive is to treat it as a like-for-like rebuild.

Old email templates, unused lists, duplicate records, and automations nobody understands do not become more valuable when they are recreated in HubSpot. They simply become new technical debt with a different logo on it.

Before anything moves, sort the existing setup into four groups.

• Keep active assets and processes that still support the business.

• Improve useful assets that need simplifying or redesigning.

• Archive historical information that should remain accessible but does not need rebuilding.

• Remove duplicates, unused assets and processes that no longer serve a purpose.

This is the bit that saves time later. It also forces the business to decide what the future process should look like, rather than treating the past as the specification. It is the same discipline we apply to every CRM migration project, whatever the platforms involved.

How does Salesforce fit into a Pardot to HubSpot migration?

For many companies considering this move, Salesforce is staying as the CRM. That means this is not only a marketing platform migration. It is also a HubSpot and Salesforce integration, data and process project.

You need clear decisions around the following.

• Which Leads, Contacts and Accounts should sync.

• Which system owns each important field.

• What happens when the same information is changed in both systems.

• How marketing activity connects to Salesforce Campaigns, Opportunities and revenue.

• How lifecycle stages, lead status, routing and sales handover should work.

• Who monitors the integration once the migration project has finished.

HubSpot’s native Salesforce integration handles the sync itself. It will not make the ownership decisions for you. We cover those decisions in detail in our guide to managing a HubSpot and Salesforce integration, and you can use our free HubSpot Salesforce integration template to document field ownership before the build starts.

A lovely new HubSpot portal is not much use if the sales team stops trusting Salesforce a week after launch.

Where HubSpot can change the conversation

The attraction of HubSpot is not simply that it looks different. For the right organisation, it can give Marketing more ownership of campaigns, content, automation and reporting, while keeping Salesforce at the centre of the sales process.

That can reduce the dependency on specialist support and help teams launch, test and improve campaigns more quickly. It can also make it easier to reuse one idea across emails, landing pages and social content, especially as AI becomes part of everyday campaign production.

But none of that happens automatically. A new platform will not fix unclear ownership, poor data or a broken handover by itself. The technology helps once the operating model makes sense. That is why we treat HubSpot onboarding as a process and data project first, and a software project second.

What should a Pardot to HubSpot migration plan include?

A sensible migration plan covers the commercial reason for moving, the future process, the data, the Salesforce integration and the people who will use the system. In practice, that means the following.

• A clear commercial reason for moving and agreed measures of success.

• A joint Sales and Marketing design for the future process.

• An audit of active Pardot assets, automation and dependencies.

• Data-cleaning rules and a clear migration scope.

• Salesforce integration design and field ownership.

• Lifecycle, scoring, routing, nurture and handover decisions.

• Reporting and attribution requirements agreed before the build.

• Testing, enablement and training, governance and a realistic cutover plan.

The order matters. Future process first, then data, then technology. Starting with a list of assets to copy usually creates more work and a worse result.

The honest answer may still be to keep Pardot

Not every review should end with a migration. Some organisations need to clean up Pardot, document the automation and fix the way Marketing and Sales work together. Our Salesforce and Pardot optimisation services exist for exactly that situation.

Others have reached the point where HubSpot is a better fit for the speed, ownership and reporting they need. For those teams, HubSpot optimisation after the move matters as much as the migration itself.

The useful decision is the one made with a clear view of the process, data, Salesforce dependency, cost, risk and internal effort involved, not the one made because everyone is fed up with the current system.

Join me for the webinar

I am also running a practical webinar on this topic at 4:00 pm on Wednesday 28 October 2026. It is called Pardot to HubSpot, Is It Time to Make the Move?

We will look at the warning signs that it may be time to review Pardot, what should and should not move, how Salesforce fits into the picture, and how to avoid carrying years of technical debt into a new platform.