Skip to content

Your old export is your best suppression list

Import an authorized CSV into a LinkedBoost lead group, then check which identities, fields, and history are available. Reconcile prior contact and exclusions before outreach. Importing leads does not guarantee that every message, reply, opt-out, or campaign state from the old system transfers.

Who this is for: Agencies moving prospect lists from another outreach tool, event export, or spreadsheet.

Why this is worth automating

How to run it, step by step

Use these prompts in Claude, ChatGPT, Instinct, or Meta Muse after connecting LinkedBoost. Review tool requests that change data or act on LinkedIn.

  1. 1

    “Stage this authorized ten-row sample. Show invalid rows, then save only the reviewed people as Migration check. Do not enroll anyone.”

    Import stages rows; saving commits the selected rows to a group. Compare identities and fields with the source. Saving does not import historical sends.

  2. 2

    “For each imported person, show recorded interactions and sequence membership. Label history we cannot confirm.”

    Compare results with your source records. Empty history does not prove a person is new.

  3. 3

    “Apply do-not-contact to these exact people from our opt-out list, then show current eligibility.”

    Review explicit exclusions. Do not treat all previous replies as opt-outs or assume an import applied the marks you need.

  4. 4

    “Show only reviewed, eligible person IDs for a new draft sequence. Ask for approval before enrolling them.”

    Enrollment can queue outreach. Resolve uncertain records instead of enrolling the entire historical group.

Plan your first run

CheckpointStarting pointWhat to check
Suggested sample10 rowsInclude a new lead, prior contact, duplicate, and opt-out
ReconciliationPer personCheck identity and eligibility as well as counts
Original recordsKeep themRetain history until migration has been checked

A practical example

An agency imports a list with a prior opt-out, someone in an active conversation, and a prospect with no recorded outreach.

Compare these source records with Migration check. Show the opt-out mark, conversation, and sequence membership for each person. Flag discrepancies. Do not infer new-contact status from missing history and do not enroll anyone.

Keep the opt-out excluded and the active conversation with its owner. The apparently new prospect needs a final history check. Hold the wider import if identities or exclusions do not reconcile. This is a migration check, not a delivery test.

What goes wrong

Assuming CSV means complete migration

Exported fields differ by vendor and settings. Messages, attachments, cadence, and campaign progress may require separate records or manual rebuilding.

Inferring a reply from the last-message field

Check direction and context in the original thread. The latest message may have been sent by your team.

Running both senders during the switch

Pause overlapping source campaigns before new enrollment. Keep a clear owner for outstanding replies.

Questions people actually ask

Can I import from another LinkedIn tool?

LinkedBoost supports CSV lead import, including Linked Helper exports. Test the fields and identities in your own file; it is not a universal campaign or conversation migration.

Will importing send anything?

Import stages rows for review; save_search commits selected rows to a lead group. Neither step enrolls people or sends outreach. Keep the sample out of active sequences while checking it.

Does importing automatically prevent duplicate contact?

Do not assume so. Reconcile prior contact, sequence membership, and explicit exclusions against your source records before approving outreach.

Start with one account and one workflow

Connect LinkedBoost, inspect the account status, and run the first research or review step. Approve exact recipients and actions before outreach, then verify completion.

LinkedIn prohibits unauthorized automation. Account limits and operator review do not eliminate restriction risk. Read the LinkedIn User Agreement and our account-risk guide before acting. Native email, CRM sync, client dashboards, and white-label reports are not offered.

Related use cases