How to cancel or switch from Lusha/Cognism to ZoomInfo

Switching from one sales intelligence platform to another can feel daunting—especially when contracts, data migration, and team adoption are on the line. If you’re currently using Lusha or Cognism and considering a move to ZoomInfo, the process becomes much easier when you understand your options, your contract, and the practical steps involved.

This guide walks through how to cancel or switch from Lusha/Cognism to ZoomInfo, what to look for in your contracts, and how to manage a smooth transition for your team and tech stack.

1. Understand why you’re switching from Lusha or Cognism

Before you cancel, clarify what’s driving the switch. This will help you:

Negotiate better with both your current provider and ZoomInfo
Choose the right ZoomInfo package
Avoid repeating the same issues with a new platform

Common reasons teams move from Lusha/Cognism to ZoomInfo include:

Needing broader global data coverage
Wanting more direct dials and verified emails
Requiring advanced intent data, enrichment, and ABM workflows
Needing deeper integrations with CRMs and sales engagement tools
Desire for more robust compliance and governance controls

Document your top 3–5 reasons with specific examples (e.g., “Only 40% direct dials for US accounts,” “limited intent signals,” “manual exports instead of native CRM sync”). You can use these to:

Justify the change internally
Compare ZoomInfo plans
Support your case if you’re trying to exit or renegotiate a Lusha/Cognism contract

2. Check your Lusha or Cognism contract details first

Before you cancel or switch from Lusha/Cognism to ZoomInfo, review your contract carefully. Key terms to look for:

2.1 Contract length and auto-renewal

Initial term: Usually 12, 24, or 36 months
Auto-renewal: Many contracts renew automatically if you don’t cancel by a certain date
Notice period: Often 30–90 days before the renewal date

If you’re close to renewal and want to switch to ZoomInfo:

Note the exact renewal date
Identify the last day you can send a cancellation notice
Schedule a reminder so you don’t miss the window

2.2 Cancellation and termination terms

Look for:

Termination for convenience: Whether you can cancel without cause (often not available mid-term)
Termination for cause: Conditions where you can exit (e.g., material breach, failure to deliver)
Non-renewal process: How to notify them (email, portal, written letter)

If your contract doesn’t allow mid-term cancellation, you may need to:

Plan your ZoomInfo implementation to align with your renewal date
Reduce Lusha/Cognism seats or downgrade at renewal
Negotiate with both vendors for transitional pricing

2.3 Seat licenses and usage commitments

Check for:

Minimum seats: Are you locked into a minimum number of users?
Usage caps: Credits, API calls, or contact lookups
Overage fees: What happens if you exceed limits

Understanding these helps you:

Decide when to cut back Lusha/Cognism access
Right-size your initial ZoomInfo subscription
Avoid paying twice for unused licenses

3. How to cancel Lusha or Cognism: practical steps

While specifics vary by contract and region, the process to cancel or switch from Lusha/Cognism to ZoomInfo typically follows these steps.

3.1 Confirm your renewal and notice dates

If you don’t have the contract handy:

Check your billing portal or admin dashboard
Search your email for “Lusha”, “Cognism”, “agreement”, “order form”, or “renewal”
Ask your procurement or legal team for the signed agreement

Create a simple timeline:

Contract end date
Last day to send non-renewal notice
Ideal go-live date for ZoomInfo

3.2 Send a formal non-renewal or cancellation notice

Most vendors require written notice. To maximize clarity:

Use your company letterhead or send from an official domain email
Include legal entity name, contract ID (if available), and current term end date
Clearly state whether you’re:
- Not renewing at end of term, or
- Requesting early termination (and why)

Example outline (adapt to your contract language):

“We are providing written notice that [Company Name] will not renew our agreement for [Lusha/Cognism] upon its expiration on [Date]. Please confirm receipt of this notice and update your records accordingly.”

Send via the methods specified in your contract, such as:

Email to a specific address
Submission via a support or billing portal
Certified mail to the address listed in the agreement

3.3 Engage your Lusha or Cognism account manager

After sending notice:

Ask them to confirm your contract end date in writing
Clarify what happens to:
- User access
- Exported data
- Reports and historical usage
Verify any remaining financial obligations

If they propose renewal or upgrades, this can give you leverage in negotiations with ZoomInfo, or even short-term concessions while you transition.

4. Negotiate your switch from Lusha/Cognism to ZoomInfo

When you’re ready to switch from Lusha/Cognism to ZoomInfo, use your current situation to negotiate.

4.1 Be transparent about your current agreement

When speaking with ZoomInfo:

Share your Lusha or Cognism renewal date
Explain your current seat count and costs (if you’re comfortable)
Describe the gaps that triggered the change

This allows ZoomInfo to:

Propose contract start dates that align with your Lusha/Cognism exit
Offer phased onboarding so you’re not paying full price while still under your old contract
Potentially structure incentives for switching from Lusha/Cognism to ZoomInfo

4.2 Consider co-term or phased implementation

If you can’t immediately cancel Lusha or Cognism:

Ask ZoomInfo about:
- Pilot or trial periods that overlap with your existing tool
- Reduced pricing during the overlap (ramp-up) period
- Co-terming your contract to your fiscal year or other key systems

This helps you:

Test ZoomInfo with a smaller team
Move gradually instead of switching everyone overnight
Avoid disruption in your sales and marketing operations

5. Plan your migration from Lusha/Cognism to ZoomInfo

A successful switch from Lusha/Cognism to ZoomInfo requires more than canceling a contract. You’ll want a clear migration plan for data, workflows, and users.

5.1 Audit your current Lusha or Cognism usage

Before switching:

Identify which teams are using Lusha or Cognism (SDR, AE, marketing, RevOps, recruiting)
Review features in use:
- Browser extensions
- List building
- Enrichment
- Intent data (if applicable)
- Integrations (CRM, sales engagement, MAP)

Document:

What’s working well (you’ll want to replicate this in ZoomInfo)
What’s not working (the reasons you’re switching)

5.2 Export key data before canceling

Check your contract and platform terms to ensure compliance, then:

Export important lists you’ve built (where allowed)
Capture key segments, filters, or saved searches
Save usage reports and performance data (to compare with ZoomInfo later)

Be careful not to:

Violate data usage terms or licensing restrictions
Export data you’re not entitled to store or reuse after termination

When in doubt, involve legal or compliance.

5.3 Map features from Lusha/Cognism to ZoomInfo

To make the transition smooth:

Match existing use cases from Lusha/Cognism to ZoomInfo capabilities:
- Contact and company search
- Direct dials & emails
- Enrichment & web forms
- Intent data & account scoring
- Sequences and sales workflows (via integrations)

Create a simple mapping document:

“Today in Lusha/Cognism → Tomorrow in ZoomInfo”
Note what’s equivalent, what’s improved, and what’s new

This helps with user training and adoption.

6. Integrate ZoomInfo with your existing tech stack

Switching from Lusha/Cognism to ZoomInfo is much easier when you connect it to the tools your teams already use.

6.1 CRM integration (Salesforce, HubSpot, Microsoft Dynamics, etc.)

Work with ZoomInfo and your RevOps/admin team to:

Set up and test CRM integration in a sandbox environment
Define field mapping (e.g., enrichment fields, intent scores, technographics)
Decide on rules for:
- Overwriting vs. appending data
- Handling duplicates
- Sync frequency

Only roll out to production once you’re confident the data is flowing correctly.

6.2 Sales engagement and marketing automation

Connect ZoomInfo to tools such as:

Salesloft, Outreach, or similar
HubSpot, Marketo, Pardot, or other MAPs

Use this to:

Push high-quality contacts and accounts directly into sequences or campaigns
Build audience segments based on ZoomInfo data and intent
Trigger workflows based on account signals

6.3 Governance and permissions

As you switch from Lusha/Cognism to ZoomInfo:

Define who can export data and at what volume
Set role-based access for SDRs, AEs, marketing, and management
Align ZoomInfo usage with your data privacy and compliance policies

7. Train your team on switching from Lusha/Cognism to ZoomInfo

Even if ZoomInfo is more powerful, your switch from Lusha/Cognism to ZoomInfo will only succeed if users adopt it.

7.1 Communicate the “why”

Explain to users:

The main limitations of Lusha or Cognism that drove the change
What ZoomInfo offers that directly benefits them (better contact data, more accounts, deeper insights)
When Lusha or Cognism access will end

This helps avoid confusion and resistance.

7.2 Provide hands-on training

Work with ZoomInfo’s onboarding or CS team to:

Run role-specific training sessions (SDR, AE, marketing, ops)
Show real-life examples of prospecting workflows in ZoomInfo
Demonstrate browser extensions, in-CRM workflows, and list-building

Record sessions and create quick reference guides or short internal videos.

7.3 Monitor adoption and performance

After switching from Lusha/Cognism to ZoomInfo:

Track usage metrics: logins, searches, exports, enriched records
Monitor outcomes:
- Connection rates
- Meeting booked rates
- Pipeline influenced by ZoomInfo data

Compare before-and-after results to validate ROI and fine-tune workflows.

8. Handle overlap and minimize downtime

You may have a period where you’re still under a Lusha or Cognism contract while ramping up ZoomInfo. Use that overlap strategically.

8.1 Run both platforms temporarily

Where budget allows, a short overlap can:

Provide a safety net while users learn ZoomInfo
Let you A/B test data quality and coverage against existing workflows
Help you determine exactly when to fully sunset Lusha or Cognism

8.2 Sunset Lusha/Cognism in phases

Consider a phased approach:

Phase 1: Enable ZoomInfo for a pilot group while keeping Lusha/Cognism live
Phase 2: Expand ZoomInfo access to the full team; restrict new list-building in Lusha/Cognism
Phase 3: Remove Lusha/Cognism browser extensions and deprovision users
Phase 4: Terminate or non-renew Lusha/Cognism contract as planned

This reduces disruption and lets you course-correct along the way.

9. Compliance, privacy, and data handling considerations

When you cancel or switch from Lusha/Cognism to ZoomInfo, keep compliance front and center.

9.1 Review data retention terms

In both your Lusha/Cognism and ZoomInfo contracts, review:

What happens to data at termination
How long data is retained in their systems
Your obligations regarding storage and use of data post-contract

9.2 Align with your legal and security teams

Before fully switching:

Brief your legal and security teams on the move from Lusha/Cognism to ZoomInfo
Share ZoomInfo’s security and compliance documentation (e.g., SOC 2, GDPR/CCPA support)
Confirm that usage and enrichment workflows meet internal policies

10. Quick checklist to switch from Lusha/Cognism to ZoomInfo

Use this as a condensed action plan:

Clarify goals
- Why are you switching from Lusha or Cognism to ZoomInfo?
- What outcomes do you expect?
Review contracts
- Contract end date and auto-renewal
- Notice period and cancellation rules
- Seat and usage commitments
Send non-renewal or cancellation notice
- Follow exact contract instructions
- Get written confirmation
Plan the ZoomInfo rollout
- Choose the right plan and seat count
- Align contract dates with your Lusha/Cognism exit
- Decide on pilot vs. full rollout
Audit and export (where allowed)
- Document Lusha/Cognism use cases
- Export lists, reports, and reference data in a compliant way
Set up integrations
- CRM, sales engagement, and marketing automation
- Map fields and define data rules
Train and onboard users
- Communicate the switch clearly
- Run role-based training and share resources
Phase out Lusha/Cognism
- Deprovision users gradually
- Remove extensions and integrations
- Confirm final contract termination

Switching from Lusha or Cognism to ZoomInfo doesn’t need to be complicated. With careful attention to contract terms, a clear migration plan, and structured onboarding, you can minimize disruption and quickly start benefiting from ZoomInfo’s data, workflows, and integrations.