How to Switch From Hotjar Without Losing Data or Tracking

To switch from Hotjar safely, audit what you use, install the new tool next to Hotjar, compare the same pages for about a week, export surveys and any recordings you need, and only then cancel. Running both in parallel is the step that prevents gaps. The whole process fits in two weeks for most sites.

Step 1: Audit what you actually use

Open your Hotjar account and list every active feature. Do not rely on memory.

Feature	Used?	Who relies on it	Must exist after the switch?
Recordings
Heatmaps
Surveys
Feedback widget
Funnels or user journeys
Integrations

Hotjar is now part of Contentsquare, and the legacy Observe, Ask and Engage plans are no longer sold to new customers, so your account may be on an older structure. Check which products you pay for. Our pricing guide explains the current tiers.

Step 2: Pick the replacement against that list

Match the must-haves to candidates. If surveys are on the list, read our survey alternatives article first, since many replay tools lack them. If budget leads, see free Hotjar alternatives. For a full market view, use the best session replay tools guide.

If you are considering BusinessMCP, read the vendor’s Hotjar alternative page including its limits: no surveys, no native mobile SDK, DOM-only replay capture and shorter retention unless you pay for the Business plan.

Key takeaway: write the must-have list before you look at any vendor’s feature page. Otherwise the vendor’s packaging defines your requirements.

Step 3: Install the new tool in parallel

BusinessMCP’s migration notes describe this sequence: install its script alongside Hotjar, enable heatmaps and recordings in the heatmap settings and choose a sampling rate, then run both tools for a week. The same logic works for any replacement.

Practical notes:

1. Install through your tag manager if you have one, so you can switch scripts on and off without code releases.
2. Mind consent. Both scripts should respect the same consent state. Test with a fresh browser profile.
3. Check page weight. Two recorders add script load. The BusinessMCP session replay page says its recorder loads after the page is interactive and ships in chunks; measure for whichever tool you choose.
4. Use a sampling rate. You rarely need every session. Sample enough to review a few dozen per page.
5. Tag a few key sessions in Hotjar that you want to compare to the new tool’s view of the same journey.

Step 4: Compare on the same pages

Choose your top three pages: for example, pricing, signup and the page with the most paid traffic. For each:

• Count rage clicks and dead clicks found in each tool. See what rage clicks are.
• Compare heatmap click maps for the same date range.
• Watch ten recordings in each tool and note whether you reach the same conclusions.
• Time how long it takes to find a problem.

Differences in numbers are normal, since tools define sessions and sampling differently. What matters is whether the conclusions agree and the new tool surfaces issues quickly.

Step 5: Export what you need

Before cancelling:

1. Export survey responses and configurations.
2. Export feedback widget data.
3. Save clips of recordings you still need as evidence, and note the date and URL.
4. Screenshot or export saved heatmaps and reports.
5. Download invoices and confirm the cancellation process and effective date.

Recordings seldom move between vendors, so decide which findings you need to retain and write them down. Our data retention article explains what each tier keeps.

Step 6: Update privacy documentation

• Update your cookie list and privacy notice with the new provider.
• Check the data processing agreement and sub-processors.
• Remove the old script and test consent again.

See GDPR compliant session replay for a checklist. This is general information, not legal advice.

Step 7: Cut over and watch for gaps

1. Remove the Hotjar script from your tag manager.
2. Keep your account active until the end of the paid period, in case someone needs old data.
3. Watch the new tool for a week to confirm sessions still arrive.
4. Tell the team where recordings and heatmaps now live, and retire links in documentation.

Common mistakes

• Cancelling before exporting surveys. The most common, and the least recoverable.
• Forgetting integrations. If Hotjar sends data to a CRM or chat tool, rebuild that link.
• Comparing raw counts. Sessions are defined differently across tools. Compare findings, not totals.
• Leaving both scripts on forever. Double recording adds weight and consent complexity.

Verdict

A switch is low risk if you treat it as a two-week project with a parallel test in the middle. The expensive mistakes happen at the end, when exports are skipped or consent is forgotten. Start with the audit table above, and use the vendor comparison pages as input, not as the decision.

What to ask the new vendor before you install

Ask a short list of questions before you add a second script to a production site.

1. What does the recorder load, and when? BusinessMCP’s session replay page says its recorder loads after the page is interactive, ships in chunks and stops after three minutes without interaction. Ask any vendor for the equivalent and measure it.
2. What is the sampling control? Coarse sampling controls are a stated limitation on BusinessMCP’s side, so check whether that matters for your volume.
3. What are the plan limits? Visitors, seats and retention differ by tier; the vendor lists them on its pricing page.
4. What do I lose? Write the list down and decide whether you can live without each item.

Timeline

Day	Task
1	Audit features, write the must-have list
2-3	Shortlist, read pricing and limits
4	Install new tool in parallel with consent tested
5-11	Collect data, review the same three pages in both tools
12	Export surveys, clips and reports
13	Remove old script, update privacy notice
14	Confirm sessions arriving, cancel at the end of the period

Compressing the timeline is possible, but the parallel week is the part not to skip.