Migration Guide
Switch to ClearView from another visitor identification tool
Switching to ClearView from another visitor identification platform is straightforward. This guide covers the general migration process and specific steps for the most common platforms: Leadfeeder, Clearbit, 6sense, and RB2B.
General Migration Process
Regardless of which platform you are migrating from, the process follows the same five steps. Most migrations can be completed in under an hour.
Set up your ClearView account
Create your ClearView account and install the tracking script on your website. Follow the Getting Started guide to go from zero to your first identified visitor. You can run ClearView alongside your existing tool during the transition.
Export your existing data
Export your historical company and contact data from your current platform as CSV. Most tools support this from their settings or admin panel. Keep this file — you will use it to seed ClearView and compare results during validation.
Import your Watch List
If you have a list of target accounts in your current tool, export them and upload the domains to ClearView's Watch List via CSV bulk import. This ensures you get alerts for the same accounts from day one.
Connect your integrations
Reconnect your CRM, Slack, and other integrations to ClearView. Most integrations use OAuth or API keys — the setup takes 2-3 minutes per tool. See our integration docs for step-by-step guides.
Validate and switch over
Run both tools in parallel for 3-5 days. Compare identification rates, data quality, and lead scores. Once you are satisfied that ClearView is performing well, remove the old tracking script and cancel your previous subscription.
Run Both Tools in Parallel
Migrating From Specific Platforms
From Leadfeeder / Dealfront
Export your data
In Leadfeeder, go to Leads > select all > Export as CSV. This gives you a list of companies with visit history. Leadfeeder does not export person-level contacts — ClearView will independently identify contacts through its own identity graph.
Tracking script swap
Replace the Leadfeeder tracker.js script tag with the ClearView tracking script. Both use async loading and have no performance impact. If you use Google Tag Manager, update the Custom HTML tag.
CRM reconnection
Disconnect Leadfeeder from your CRM (HubSpot, Salesforce, Pipedrive) and connect ClearView instead. ClearView syncs to the same Contact and Company objects — your existing CRM data is not affected.
Key differences
ClearView adds person-level identification (Leadfeeder only identifies companies), an Audience Builder with 254M+ records, and auto-generated outreach drafts. Lead scoring methodology differs — expect score values to change but prioritization to remain similar.
From Clearbit Reveal
Export your enrichment data
Clearbit stores enrichment data in your CRM. Export your Clearbit-enriched contacts from HubSpot or Salesforce as CSV. You can import these into ClearView's enrichment pipeline to compare data quality.
Remove Clearbit scripts
Remove the Clearbit Reveal JavaScript snippet and any Clearbit API calls from your website. Replace with the ClearView tracking script. If you use Clearbit's HubSpot integration, disconnect it before connecting ClearView.
API migration
If you call Clearbit's Reveal or Enrichment API, update your code to use ClearView's /api/v1/resolve endpoint. The request format is similar — pass an IP or domain and receive company + contact data.
Key differences
ClearView includes visitor tracking, lead scoring, and Watch List alerts — features that require separate tools when using Clearbit. ClearView's Audience Builder replaces Clearbit Prospector for list building.
From 6sense
Export your account lists
Export your 6sense account lists and segments as CSV. Upload the company domains to ClearView's Watch List so you continue to monitor the same target accounts.
Replace the 6sense tag
Remove the 6sense JavaScript tag from your website and replace it with ClearView's tracking script. If you use a tag manager, swap the Custom HTML tags.
Intent data comparison
6sense uses third-party intent data (keyword research, content consumption). ClearView measures first-party intent (actual visits to your website). The signals are different — ClearView's lead scores reflect direct engagement with your site rather than inferred topic interest.
Key differences
ClearView is significantly simpler to set up and operate than 6sense. You lose third-party intent signals but gain person-level identification, an Audience Builder, and transparent scoring. Most teams find first-party signals more actionable for direct outreach.
From RB2B
Export your visitor data
Export your RB2B visitor list as CSV from the dashboard. This gives you a list of identified visitors and companies for comparison during the validation period.
Script swap
Replace the RB2B tracking pixel with ClearView's tracking script. Both are lightweight async scripts — the swap is a single line change in your HTML head.
Webhook migration
If you use RB2B's webhook notifications, set up equivalent webhooks in ClearView under Settings > Webhooks. ClearView supports the same event types (new company, hot lead, returning visitor) with richer payloads.
Key differences
ClearView adds lead scoring, Watch List alerts, Cohort Insights, an Audience Builder, CRM integrations, and team management — features not available in RB2B. Person-level identification coverage may differ as each platform uses different identity resolution methods.
Migration Validation Checklist
Before removing your old tool, verify these items during the parallel-run period:
Need Help Migrating?