Service

Tracking and attribution that survive a move to HubSpot

A CRM migration or a new website is the most common moment for attribution to break quietly. Source fields get mapped wrong, original source history is lost, redirects strip UTMs and ad platforms stop receiving conversions from the old system. I rebuild tracking around the migration and test every path before cutover, so reporting does not start again from zero.

By Vladimir Cvetkoski · Last updated 6 October 2026

Who it is for

This is for you if

→Companies moving to HubSpot from Salesforce, Pipedrive, Marketo or another CRM or marketing automation tool
→Teams launching a new website or moving domains while running paid campaigns
→Marketing ops leads who own the migration but not the tracking code, GTM or ad platform side
→RevOps teams that need source reporting to continue across the old and new systems

Symptoms

Signs you need this

→After go-live, new contacts arrive with Direct or Offline as their source. See why HubSpot shows so much Direct traffic.
→Imported contacts all show the import as their source, and the original channel history is gone.
→Old landing page URLs redirect to the new site without their UTMs.
→Google Ads offline conversions stopped when the old CRM was switched off. See offline conversions missing.
→Forms on the new site do not capture the hidden fields the old forms did. See HubSpot form UTMs missing.

What I do

What the work covers

Source history preserved

Original source and channel history from the old system carried into dedicated HubSpot properties, so reports can combine old and new records.

Source field mapping

Fields like Salesforce Lead Source, Pipedrive source or Marketo acquisition program mapped to HubSpot properties, with the decisions documented.

UTM taxonomy

One consistent set of rules for tagging campaigns across every channel, so new data is clean from the first day.

Ad platform conversions re-pointed

Google Ads, Meta and LinkedIn conversions moved from the old system to HubSpot, with click ID capture rebuilt on the new forms.

Redirects that keep parameters

Redirect rules checked so old URLs pass UTMs and click IDs through to the new pages.

Pre-cutover test plan

Tagged test journeys through every channel and form, run on the new setup before the switch and again right after.

How it works

Three steps

Map old to new

I document how source data works in the old system and agree how each field, form and conversion maps to HubSpot.

Build before cutover

Tracking code, forms, hidden fields, redirects and ad platform connections set up and tested before the switch.

Cut over and verify

On go-live I re-run the test journeys, watch the first real contacts and conversions, and fix anything that slips.

Scope and timeline

Typical scope

Timeline: I get involved 2 to 4 weeks before cutover
Best time to start: Before the migration plan is final, so tracking is part of it and not an afterthought
Access needed: Old and new CRM, GTM, website or CMS, DNS or redirect settings, and each ad account

I work alongside whoever runs the data migration. I own tracking, source data and ad platform conversions, not the full CRM data move.

What you get

At the end you have

→Source reporting that continues across the old and new systems
→New contacts arriving in HubSpot with the right source from day one
→Ad platforms still receiving conversions after the old system is switched off
→A documented UTM taxonomy and source field map

Architecture

How the pieces connect

01
Old CRM
Salesforce, Pipedrive or Marketo source fields
02
Field mapping
Legacy source into HubSpot properties
03
New site
Redirects keep UTMs and click IDs
04
HubSpot
Tracking code, forms, hidden fields
05
Ad platforms
Conversions re-pointed to HubSpot

Source data has to survive three moves at once: old records into HubSpot, old URLs to new pages, and ad platform conversions from the old system to the new one.

From the blog

11 min read

HubSpot Original Source vs Latest Source: what they really record

What HubSpot Original and Latest Traffic Source record, when each one changes, how visits get classified, and how to add your own first and last touch fields.

Questions

Migration Tracking Rebuild: common questions

Yes. HubSpot lets you edit Original Source per record, in bulk or by workflow, but editing it clears the drill-down values. So I usually keep the full history in dedicated legacy source properties, set Original Source only where it adds something, and build reports that combine the two.

Before the field mapping is finalised. Source fields, hidden form fields and ad platform connections are much easier to get right in the plan than to repair after go-live, when the old system may already be switched off.

It often does. New forms lose hidden fields, new templates miss the tracking code, and redirects from old URLs drop query strings. Each of those is easy to test before launch and hard to notice after.

If Google Ads imports conversions from Salesforce, they stop when the connection stops. I set up the replacement from HubSpot and run both in parallel where possible, so bidding does not lose its signal during the switch.

No. I work with whoever moves the records, deals and workflows, and I own the tracking, source data and ad platform side. If you do not have a migration partner yet, tell me and I will say what to look for.

Describe what you are seeing

Send a few lines about what looks wrong. I reply within 1 business day and tell you whether it needs an audit, a fix, or nothing at all.

Describe your problem