--- title: "RB2B Migration Checklist: Data, Routing and Continuity" description: "An RB2B migration should preserve exclusions, field mappings, account ownership and historical visit context." canonical_url: "https://www.leadpipe.com/blog/what-are-the-alternatives-to-rb2b/" source_url: "https://www.leadpipe.com/blog/what-are-the-alternatives-to-rb2b/" md_url: "https://www.leadpipe.com/blog/what-are-the-alternatives-to-rb2b.md" content_type: "article" pubDate: "2026-01-17T00:00:00.000Z" last_updated: "2026-09-15T00:00:00.000Z" --- # RB2B Migration Checklist: Data, Routing and Continuity Quick answer An RB2B migration should preserve exclusions, field mappings, account ownership and historical visit context. Choose the replacement separately, then compare delivery before removing the old setup. An RB2B migration should preserve exclusions, field mappings, account ownership and historical visit context. Choose the replacement separately, then compare delivery before removing the old setup. This is a Leadpipe-authored buying guide. Product statements are based on the linked vendor references; evaluation steps are recommendations, not reported test results. ## Start with the replacement decision Use the [RB2B alternatives guide](/blog/rb2b-alternatives/) to build the shortlist. This page covers the migration work once you have chosen a candidate. Keeping those decisions separate prevents a long vendor list from hiding operational risks. ## Inventory the current workflow | Item | What to preserve | | --- | --- | | Plan and output | Whether records are companies, contact profiles or enriched contacts | | Exclusions | Customers, staff, partners, competitors and excluded URLs | | Destinations | Slack or Teams channels, CRM fields and downstream workflows | | Ownership | Existing account owner and rules for new accounts | | History | Required visit records, timestamps and account notes | | Suppression | Opt-outs, deletion requests and downstream exclusions | [RB2B documents exclusions and plan-specific integrations](https://www.rb2b.com/pricing). Export or record the settings you actually use. Do not assume a feature absent from an old comparison is absent from your account. ## Validate before switching delivery Install the candidate only on approved pages and under the site’s established privacy configuration. Compare a common traffic window. Label the source clearly and prevent duplicate notifications or outreach while both systems run. Check a known customer, an excluded URL, a repeat visitor and a new account. The goal is to demonstrate delivery and governance as well as successful identification. Confirm that a CRM update preserves account ownership and does not overwrite trusted fields unexpectedly. ## Make the cutover reversible Record who can pause delivery, restore the prior integration and resolve duplicate records. Preserve needed exports before ending access, subject to contract terms. Remove the old script when the new workflow is accepted and document which system owns the next update. A successful migration produces a stable workflow with clear ownership. It does not require a higher raw record count if the records are more relevant or easier to use. Compare accepted output and operating cost using the same definitions before and after cutover. ## Where Leadpipe fits Leadpipe supports both account-level and person-level workflows. Its [IP to Company API](/product/ip-to-company/) retrieves stored company information from an IPv4 or IPv6 address; its separate [Identification product](/product/identification/) supplies eligible visitor records and activity. Choose company context for account research and person-level output when the action requires a specific visitor. A company lookup returns no people or visits. Confirm API eligibility and its separate lookup allowance in the [official documentation](https://docs.leadpipe.com/ip-to-company/introduction). Person-level coverage is strongest in the US. EU/UK traffic defaults to company-level identification; person-level requires affirmative consent. Fields can be missing, so judge required output on your actual traffic. If you need research signals from outside your website, evaluate [Orbit](/product/orbit/) separately and check its audience allowances. The [current pricing page](/pricing/) lists Pro 500 at $147/month for 500 identification credits. The trial is **7 days or 500 profiles, whichever comes first, no card**. Confirm the delivery and data-use requirements of your chosen plan. Use the [vendor evaluation kit](/resources/visitor-identification/) to record the same acceptance criteria for every candidate. [Start a Leadpipe trial](https://dashboard.leadpipe.com/auth/signup) when website identification is the requirement you want to measure. ## Related decisions Browse the [comparison directory](/compare/) for alternatives and head-to-head guides. Use the [software buying guide](/blog/b2b-website-visitor-identification-software/) to define requirements and the [person-versus-company guide](/blog/person-level-vs-company-level-visitor-identification/) to interpret identification results. ## Related vendor guides - [RB2B Alternatives: Compare Visitor Data and Workflows](/blog/rb2b-alternatives/) - [Leadpipe vs RB2B: Plans, Fields and Visitor Workflows](/blog/leadpipe-vs-rb2b/) - [RB2B vs Clearbit: Visitor Alerts or HubSpot Buyer Intent?](/blog/rb2b-vs-clearbit/) ## Sources and review basis Published by Leadpipe. Vendor references support product descriptions; recommendations reflect our assessment of fit. Confirm current plan and contract terms before buying. - [Leadpipe IP to company API](https://docs.leadpipe.com/ip-to-company/introduction) - [RB2B product / buying reference](https://www.rb2b.com/pricing) - [Leadpipe product / buying reference](https://www.leadpipe.com/product/identification/) - [Leadpipe pricing and plan allowances](https://www.leadpipe.com/pricing/) [Explore all comparisons and our evaluation method →](/compare/)