The short answer
- Count active and paused campaign contacts separately from stored history when comparing plans.
- Instantly’s plan comparison includes active and paused campaign contacts in its uploaded contact limit.
- Smartlead’s All Leads guide excludes archived leads outside campaigns from active limits, with a restricted initial rollout.
- If campaigns share a workspace boundary, consider Instantly; if they need client-associated entries, examine Smartlead.
Count the workload before comparing plans
Start with the records and sending accounts your team needs, then ask each vendor how its plan counts them. This guide compares documentation from Instantly and Smartlead.
Instantly’s plan comparison counts active and paused campaign contacts against uploaded contact limits. Pausing a campaign contact does not release that capacity.
Smartlead’s All Leads guide says archived leads outside campaigns do not count toward active limits. Its initial rollout targets Unlimited users with 60K+ leads, so do not assume that storage arrangement applies to every plan.
Suppose an agency pauses a campaign but wants to retain its leads for a later review. Record those leads separately from the next campaign’s intended audience. The distinction affects how much capacity the agency needs and which history it must preserve.
Request the sending-account allowance and any account-specific charges for the proposed plan. The documentation compared here does not provide a comparable sending-account allowance for both products. Keep sending accounts distinct from contacts and monthly send volume when requesting a quote.
Compare limits and controls
Match the documented unit to the boundary and output your team needs. The table is a starting point for a plan discussion.
| Product | Capacity | Suppression and export |
|---|---|---|
| Instantly | Uploaded contact limits include active and paused campaign contacts. | Workspace-wide blocklist; lead downloads from campaigns, CRM and All Leads. |
| Smartlead | Archived leads outside campaigns do not count toward active limits; initial rollout targets Unlimited users with 60K+ leads. | Client-associated block entries; separate campaign lead and inbox exports. |
Source: Instantly: uploaded contact limits, Instantly: blocklist scope and Sheets routes, Instantly: lead downloads, Smartlead: All Leads storage and campaign push, Smartlead: client blocklist scope, Smartlead: lead and inbox exports
Instantly’s download guide covers leads from campaigns, CRM and All Leads. It does not prove portability of full reply history or analytics.
Smartlead’s export guide separates campaign lead and inbox exports. The inbox export includes sequence and reply details, sent and replied timestamps, and an unsubscribe flag.
A file retained outside the product may preserve context without making it searchable in the replacement. Compare actual columns with the destination’s import mapping before treating the handoff as complete.
Map the suppression boundary
Draw the boundary around every campaign that should receive a do-not-contact rule. A label such as global does not answer which client or workspace is covered.
Instantly’s blocklist guide describes workspace-wide blocking. Its Blocklist tab is checked during imports and across ongoing campaigns.
The destination matters when a spreadsheet supplies the list. Instantly’s blocklist guide distinguishes a Google Sheet imported into the Blocklist tab from its separate Google Sheets Blocklist connection, which checks imports only.
Smartlead’s blocklist guide associates entries with clients; unassigned entries protect unassigned campaigns. An agency should map an entry to each relevant client boundary.
Smartlead troubleshooting says entries and campaigns must share client scope. Domain matches are exact, and domains should omit protocol and www. It warns that already-queued messages may precede blocking; its timing wording is unclear.
A duplicate check has a separate job from suppression. Instantly’s duplicate guide says workspace-level checks are on by default and can be disabled, while file-level duplicate removal always runs. Test both behaviors separately.
Preserve the record before switching
Plan the exit while the old account still holds the records. Decide which data must work in the destination and which can remain a readable archive.
Smartlead’s API reference describes a separate per-lead campaign message-history endpoint. Its existence does not prove that a replacement can import that history.
Save suppression entries with their client or workspace context. Reconcile the exported records against the destination’s rules, then record any fields that cannot be restored. Keep a separate account of unsubscribe state and conversation context.
Import settings can change what is checked at intake. Smartlead’s API reference describes settings that can bypass global-block and unsubscribe checks; an accepted import alone does not prove send eligibility.
Before removing a block entry, preserve available history. Smartlead troubleshooting warns of possible email-thread loss on removal, so confirm the consequence before making that change.
The Instantly product guide and Smartlead product guide cover each workflow in more detail. The comparison puts their suppression boundaries side by side.
Test the plan and the handoff
Use the same inactive fixtures for each candidate and record the expected result before inspecting the product. A useful evaluation leaves uncertain behavior visible.
Use the software trial guide to record the same expectations and observations for both candidates. Do not infer a successful block from an absent row alone.
Common questions
What is the best cold email software for an agency?
Consider Instantly when a shared workspace suppression boundary fits. Examine Smartlead when client-associated entries fit the way the agency assigns campaigns. Test the intended scope and handoff in either case.
Do paused leads count toward a cold email plan?
Instantly’s plan comparison includes active and paused campaign contacts in uploaded contact limits. Ask each vendor how your proposed plan treats paused records.
Does a global blocklist cover every client?
Smartlead’s blocklist guide assigns entries to clients; unassigned entries protect unassigned campaigns. Map entries to the client scope of each campaign.
Can I move replies when I switch cold email software?
Smartlead’s export guide describes a separate inbox export with reply details. The destination’s ability to import that history needs its own check.
Are sending accounts the same limit as contacts?
Treat sending accounts and contact capacity as separate plan questions. Request the allowances and charges for your proposed workload.
Sources and scope
We read the linked Instantly and Smartlead documentation on October 29, 2026. We have not run either product, measured deliverability or tested the proposed workflow.
Confirm current plan allowances, sending-account terms, storage eligibility and the export fields your destination can restore.
Source references
- Instantly: uploaded contact limits
Checked 2026-10-29. Supports inclusion of paused contacts in capacity.
- Smartlead: All Leads storage and campaign push
Checked 2026-10-29. Supports rollout limits and documented campaign-push switches.
- Instantly: blocklist scope and Sheets routes
Checked 2026-10-29. Supports workspace scope and the distinct Sheets routes.
- Instantly: lead downloads
Checked 2026-10-29. Supports lead download locations.
- Smartlead: client blocklist scope
Checked 2026-10-29. Supports client-specific and unassigned entries and CSV transfer.
- Smartlead: lead and inbox exports
Checked 2026-10-29. Supports the separate export types and inbox fields.
- Smartlead: blocklist troubleshooting
Checked 2026-10-29. Supports client and domain matching, queue uncertainty and thread-loss warning.
- Instantly: duplicate checks
Checked 2026-10-29. Supports workspace and file-level duplicate checks.
- Smartlead: API imports and message history
Checked 2026-10-29. Supports import overrides and the separate message-history endpoint.