Pardot · migration to Marketing Cloud Next
The migration is not the hard part.
Deciding when is.
Moving off Pardot is a known quantity: assets, programs, scoring, forms, sync. What costs teams money is moving in the wrong quarter, or rebuilding automation that should have been retired instead. Scope it below before anyone quotes you.
Elapsed
-
Fixed price
-
Scale
-
Engagement
-
What makes up the price
Phases
Every line above is a fixed price, not a range. It becomes the contract price once the written scope is signed, and it cannot move upward afterwards. Everything is built inside your own org and documented as the work happens, so nothing here depends on any one person staying available.
The decision before the project
Three honest answers about timing.
Salesforce has an interest in you moving. You have an interest in moving once, at the right moment, with the right things left behind. Those are not the same interest.
Move now if your renewal is inside twelve months
Migrating while you still hold a working Pardot instance is dramatically safer than migrating after it is switched off. You keep a fallback, you can run both in parallel for a month, and you can compare engagement numbers between the two rather than trusting that they transferred correctly.
Wait if your data is the actual problem
A migration copies your architecture into a new place. If scoring has been broken since 2023 and sync drops prospects silently, migrating relocates both problems and adds a new platform to learn. Fix the foundation, then move. That order costs less in total, even though it looks slower on a plan.
Do not move at all if nobody uses what you have
Some teams discover during discovery that they are paying for marketing automation to send four emails a quarter. Migration is the wrong answer to that. So is a rebuild. The honest recommendation is sometimes to reduce the licence and spend the difference elsewhere, and I will make it if it fits.
What actually moves
And what should be left behind on purpose.
The instinct is to move everything, because everything was paid for once. That instinct is what makes migrations expensive. A migration is the cheapest opportunity you will ever get to delete things.
Worth moving
- Prospect records and their engagement history, which is the asset
- Programs that produced a measurable outcome in the last twelve months
- Forms and landing pages still receiving traffic
- Scoring and grading logic, but rebuilt rather than copied
- The Salesforce connector configuration and field mappings
Leave behind
- Engagement Studio programs nobody has opened since 2023
- Lists built for a campaign that ended, of which there are always dozens
- Automation rules that duplicate what a flow already does
- Custom fields with under five percent population
- Templates for a brand refresh that happened two refreshes ago
Questions
Asked often enough to answer here.
Will engagement history be lost when migrating from Pardot?
Not if the export happens before the instance is decommissioned, which is the single strongest argument for migrating early. Prospect activity history is the asset that took years to accumulate and cannot be recreated. It is exported first, before anything is built.
Can Pardot and Marketing Cloud Next run in parallel?
Yes, and I recommend a month of it where licensing allows. One live program on each side, same audience segment, and you compare the numbers. It is the only honest way to know the migration worked, rather than assuming it did because nothing threw an error.
What happens to the Pardot scoring model during migration?
It gets rebuilt rather than copied, and this is deliberate. Most scoring models in Pardot were tuned in a different year for a different buying process, and the top-scoring prospects are frequently accumulating points from behaviour that no longer indicates intent. Migration is the moment to fix that, not to preserve it.
Is Data Cloud required for Marketing Cloud Next?
Depends on what you are trying to do, and the answer is no more often than the marketing suggests. If your segmentation lives on Salesforce fields and behaves, you may not need it yet. That question gets answered in discovery with your actual data rather than by a licence conversation.
When is the right time to migrate off Pardot?
Directly. An agent reasoning over marketing engagement reads whatever the migration leaves behind. Migrating dead programs and broken scoring gives the agent the same wrong picture in a newer platform. If agents are on the roadmap, say so and the target architecture is built accordingly.
Bring the estimate to the call.
Thirty minutes. Read out what the estimator gave you and I will tell you where it is optimistic, where it is generous, and whether the timing is right at all.
Serhii Skrypnyk · RevOps Architect · 7 Salesforce certifications · on the platform since 2018