The short answer

  • LinkedIn’s policy does not permit third-party software or extensions that scrape or automate activity on its website; it describes account restrictions.
  • If you need a documented way to preserve custom lead fields, investigate HeyReach’s API alongside its CSV export limit.
  • Count senders and seats for your actual team, then obtain the checkout amount and any add-on charges.
  • Before changing a live campaign, trace the people already in progress and their sender assignments.

Start with LinkedIn’s policy

Decide whether the platform policy is acceptable before comparing campaign features. This guide compares documentation from HeyReach and Expandi with LinkedIn’s own policy.

LinkedIn’s automated activity policy says it does not permit third-party software or extensions that scrape or automate activity on its website. LinkedIn describes account restrictions for automation.

A vendor’s description of its precautions does not change that policy. The policy does not provide a probability of restriction for a particular account, so a buyer cannot turn it into a reliable forecast of account loss.

Give the account owner the policy before deciding whether to proceed. Map the work that depends on the account, including ongoing conversations, so the owner can weigh the consequences of a restriction. A paid account should not be treated as permission for prohibited automation.

If the policy rules out automation for your team, plan the outreach process around activity the account owner is willing to perform. Record that decision before investing time in sequence design or importing a prospect list.

Compare the sender commitment

Count the people who need to send and the client boundaries they need before comparing a monthly figure. A sender, seat and workspace answer different questions, so request a quote for your actual configuration.

HeyReach pricing displays Growth at $79 per month per sender. HeyReach also displays Agency at $999 and Unlimited at $2,999; the Unlimited description has a 300-sender fair-use ceiling.

Expandi pricing displays Business at $99 per month and custom Agency pricing for 10+ seats. Expandi charges extra for image and GIF personalization and video integration.

Documented pricing and operating differences
ProductBilling unitLimit that mattersControl or export
HeyReachGrowth: $79 per month per senderUnlimited: 300-sender fair-use ceilingLaunched campaign list cannot be replaced; lead-list CSV excludes custom variables
ExpandiBusiness: $99 per month; Agency: customAgency: 10+ seats; personalization add-ons cost extraCSV mapping and sequence rebuild on migration; historical tool analytics do not transfer

Source: HeyReach: Pricing, HeyReach: Launch your first campaign, HeyReach: Leads Screen Overview, Expandi: Current pricing, trial and paid add-ons, Expandi: Migration guide

For example, an agency with separate client teams should count each sender and identify the client workspace needed before requesting a quote. HeyReach’s pricing page says workspaces separate client data. A workspace boundary also matters when checking exclusions.

Expandi’s annual pricing copy describes both 20% off and two months free. Those descriptions yield different amounts, so use the actual checkout or written quote instead of calculating an annual price from either phrase.

Expandi’s pricing FAQ says its seven-day trial renews into the selected billing period unless cancelled. Put the renewal date and cancellation owner on the evaluation plan before the trial starts.

Plan changes to a live campaign

Treat an edit to a running campaign as a handoff of people and their progress, not just a change to message text. Decide who is responsible for reconciling the old campaign with the new one.

HeyReach’s launch guide says the selected lead list cannot be replaced after launch and describes duplication as the workaround. Its exclusion rules are workspace-scoped; previous sender conversations count only when registered in Unibox.

For a worked example, imagine a client asks to replace the list after a campaign starts. Duplicate the campaign as HeyReach describes, then reconcile the original list with the replacement before deciding who should enter the new campaign.

Keep a record of each person’s campaign state and any conversation already underway. A list of names alone is too thin a handoff for deciding whether someone should receive a first message again.

HeyReach’s list API guide says adding leads to a list will not start them in a campaign that has finished or consumed its list. Direct campaign-add endpoints are separate. Reconcile the result against the intended enrollment.

For Expandi, ask to see an edit made to a live sequence with a representative contact already in progress. Record what happens to that contact and to the sender assignment. The documentation compared here does not settle that workflow.

Preserve the fields you need to leave

Choose an exit route before loading custom data. A downloadable list is useful only if it carries the fields your next process needs and you can connect those fields to the right person.

HeyReach’s leads screen guide says its CSV export includes default columns and excludes custom variables. Save the original input and its mapping alongside any export; do not assume the CSV is a complete backup.

HeyReach’s list API example includes customFields name and value pairs in a paginated response. It describes up to 1,000 leads per request. The sample host and filter labels need validation before using that route.

HeyReach’s import guide warns that default variable names take precedence over colliding CSV mappings. API and Clay imports require firstName, lastName and profileUrl; the guide warns missing fields can fail silently.

Compare imported and failed counts with the input file, then inspect a few records by their profile URLs. Keep the names of custom fields consistent in the source file and in the destination mapping.

HeyReach’s Auto-Tag guide says the latest campaign tag replaces the prior workspace-wide tag. Lead-list CSV includes tag provenance, while campaign CSV includes a tag only if it was generated there. A current tag alone is not a full campaign history.

Expandi’s migration guide describes CSV mapping and rebuilding sequences. Expandi says historical tool analytics do not transfer, while LinkedIn conversations remain on LinkedIn. Preserve campaign contact states separately before closing the old account.

Expandi’s placeholder guide describes custom placeholders in My Network, populated manually or by CSV. It also describes clearing imported placeholders before a corrected import. Test a small mapping before relying on a bulk handoff.

Test the workflow before committing

Use a small, authorized sample to trace the handoff from source file to campaign record and back out. Review LinkedIn’s policy with the account owner before choosing any activity for the evaluation.

Keep the output from each step with the quote. If a vendor demonstration differs from the written documentation, record the plan and route used and ask for the difference in writing.

When email is part of the same outreach workflow, use the Instantly guide to examine its operating choices. The Instantly and Smartlead comparison helps assess the email side of the handoff. Keep a shared record of who owns each contact’s next action.

Common questions

Does LinkedIn allow automation tools?

LinkedIn’s policy says it does not permit third-party software or extensions that scrape or automate activity on its website. LinkedIn describes account restrictions for automation.

Which LinkedIn automation tool is best for an agency?

If separate client workspaces and a per-sender Growth price fit your team, investigate HeyReach pricing. If you need a custom quote for 10+ seats, consider Expandi’s Agency offering. Review LinkedIn’s policy first.

Can I replace a list in a running HeyReach campaign?

HeyReach’s launch guide says the selected list cannot be replaced after launch. It describes duplicating the campaign as a workaround.

Can I export HeyReach custom variables?

HeyReach’s leads guide says its CSV export excludes custom variables. HeyReach’s API example includes customFields; validate the request and reconcile its output.

Will Expandi import my old campaign history?

Expandi’s migration guide says historical tool analytics do not transfer. It describes rebuilding sequences and preserving contact states; LinkedIn conversations remain on LinkedIn.

What happens after the Expandi trial?

Expandi’s pricing FAQ says the seven-day trial renews into the selected billing period unless cancelled. Verify the amount and cancellation deadline at checkout.

Sources and scope

We read LinkedIn, HeyReach and Expandi documentation on October 29, 2026. We have not run the products or tested campaign edits, exports or support.

Confirm current pricing, plan limits and the export route with the vendor before committing. Review LinkedIn’s current policy with the account owner.

Source references

  1. LinkedIn: Automated activity on LinkedIn

    Checked 2026-10-29. Source for automated activity on linkedin.

  2. HeyReach: Pricing

    Checked 2026-10-29. Source for pricing.

  3. Expandi: Current pricing, trial and paid add-ons

    Checked 2026-10-29. Source for current pricing, trial and paid add-ons.

  4. HeyReach: Launch your first campaign

    Checked 2026-10-29. Source for launch your first campaign.

  5. HeyReach: Leads Screen Overview

    Checked 2026-10-29. Source for leads screen overview.

  6. Expandi: Migration guide

    Checked 2026-10-29. Source for migration guide.

  7. HeyReach: Adding to a list does not necessarily enroll in a campaign

    Checked 2026-10-29. Source for adding to a list does not necessarily enroll in a campaign.

  8. HeyReach: API lead-list retrieval includes custom fields

    Checked 2026-10-29. Source for api lead-list retrieval includes custom fields.

  9. HeyReach: Custom variable imports and silent missing-field failures

    Checked 2026-10-29. Source for custom variable imports and silent missing-field failures.

  10. HeyReach: Auto-Tag provenance and export scope

    Checked 2026-10-29. Source for auto-tag provenance and export scope.

  11. Expandi: Create and edit placeholders

    Checked 2026-10-29. Source for create and edit placeholders.