How to switch LinkedIn lead generation agencies without losing prospect context

The outgoing agency has sent a contact list. The new team can open it, but cannot tell who has already replied, which follow-ups are still scheduled or who expects an answer tomorrow. Starting another campaign would turn a delivery problem into a prospect problem.

To switch LinkedIn lead generation agencies, pause the old outreach, agree what information can be handed over, test the export and assign the outstanding conversations. Close the outgoing provider's access after that work is accepted. The receiving team can be another agency or your own staff; choosing a new supplier is separate from getting control of the current work.

This guide covers the end of an agency engagement. For an individual lead moving from an SDR to a sales rep, use the narrower sales-handoff guide.

Stop the old work before the new team starts

Agree an effective pause time with the outgoing agency and the people responsible for live conversations. Record the time zone, the campaigns covered and any exceptions. Someone may still need to answer an existing question or attend a meeting; that does not require restarting a prospecting sequence.

Ask the outgoing provider to show the current state of scheduled work in the tools it used. Distinguish an instruction to pause from a verified stopped state. If a scheduled action cannot be inspected or cancelled, record the uncertainty and keep the receiving team from contacting the affected people until it is resolved.

Include work outside LinkedIn if it was part of the engagement: scheduled emails, meeting reminders and tasks assigned to staff can survive a campaign pause. The client should keep one transition owner who can reconcile those exceptions with both teams.

LinkedIn's automated-activity policy prohibits third-party software and browser extensions that automate activity on its website. A new provider, a slower schedule or a fresh list does not establish permission. Review the actual method before deciding what work should resume.

Separate the member account from the agency's deliverables

A handover inventory should name each asset, who controls it, what the client is entitled to receive and who may access it. A prospect list, a message draft, a paid database licence and a member's LinkedIn account have different constraints.

LinkedIn's User Agreement, section 2.2, says members must not share or transfer their accounts. As between a member and an employer, the account belongs to the member. Do not ask the outgoing agency to transfer a personal profile, its connections or its password to another operator. Business-service seats and Page roles need their own access review; they do not turn a member account into a transferable client asset.

For the agency's work, inspect the agreement rather than assume everything is included. Identify the approved audience rules, researched records, campaign definitions, approved messages, client-supplied evidence, reports and outstanding tasks. Record any licensed source data or agency material that the client cannot reuse. An agency's right to a template and a client's permission to process a prospect's information are different questions.

If the agreement is unclear, resolve the missing deliverable or access right before commissioning a migration. Importing a file cannot settle a contract dispute.

Ask for the state behind the names

The receiving team needs enough information to decide what may happen next. Request the necessary, authorized fields rather than a copy of every file the agency holds:

• A stable prospect identifier, verified profile link and existing CRM record reference, where available.
• The source of the record, relevant audience evidence and unresolved assumptions about fit.
• The last confirmed action, its date and channel, and whether the recorded state is current or uncertain.
• The prospect's actual request or objection, any promise already made, and the person responsible for completing it.
• Contact restrictions, declined outreach and any approved future contact condition.
• The campaign or list the record belonged to, with the current campaign state and any outstanding scheduled work.

Keep an operational state such as “message queued” distinct from “message sent.” Keep “asked for pricing” separate from “qualified opportunity.” The new agency should inherit the evidence needed to make a decision, including facts that make the pipeline look less attractive.

An export can have narrower coverage than its label suggests. HubSpot's record-export documentation says its standard record export downloads current property values and associations; activities such as calls and notes have separate export routes. That is a HubSpot-specific example, not a claim about every CRM. For the system you use, check which history, notes, attachments and relationships actually travel with the file.

When an authorized conversation cannot be exported, agree a permitted way to preserve the decision-relevant context, such as a restricted summary linked to the original record. Mark what is missing. Do not manufacture a complete-looking history from the outgoing account manager's memory.

Carry the stop decisions through the import

Someone who objected to outreach must not become an active target because the new provider sees a blank status field. A fresh supplier is not a fresh relationship with that person.

For processing subject to the UK GDPR, Article 21 gives people a right to object to direct marketing and requires that processing for that purpose to stop after an objection. Other jurisdictions have their own requirements. Have the client's privacy or compliance lead decide what minimum restriction information must be retained, how it may be shared and who may access it. Keeping an entire conversation archive is not automatically justified by the need to avoid another message.

Check stop states separately from positive pipeline records. A sample of promising replies will not reveal whether declined prospects were silently omitted. Preserve the scope of a restriction and its source; if the scope is unclear, hold contact while the client resolves it.

Test the handover before accepting it

Start with a small sample that tests the ways the transfer could fail: an unanswered question, an agreed next step, a declined prospect, an uncertain state and a record associated with an existing deal. The client chooses the sample and traces it back to the authorized source. Do not let the outgoing provider demonstrate only its cleanest records.

Here is a fictional case. A prospect asked for a security document by Thursday. The CSV says “positive reply,” the old campaign still has a follow-up queued and the new agency has assigned nobody to the request. The contact imported successfully. The handover failed. Acceptance needs the real request, the agreed deadline, a named receiver and a verified decision about the old queued action.

Then reconcile the export and import. Record the exported count, imported count, duplicates, excluded records and failures. Explain each difference rather than force the totals to match by adding missing-looking people. Resolve duplicate LinkedIn leads against existing records before starting another sequence.

Ask the receiver to demonstrate that it can open the permitted context, identify restrictions and find the outstanding next action. A file download, a successful import and an accepted handover are separate events. Log any exception, its owner and the decision that will close it.

Close access and data obligations explicitly

After the necessary information is received and accepted, remove the outgoing provider's permitted access to client-controlled workspaces and integrations. Review users, business-service roles, API keys and connected applications individually. Record what was removed and who verified it; do not rotate credentials blindly and interrupt the receiving team's authorized work.

If a member password was shared, the member should secure their own account and review access through LinkedIn's controls. Password sharing should not be continued as the migration method.

Data closeout depends on the agreement, actual processing roles and applicable law. The ICO's controller-and-processor guide explains that those roles depend on who determines the purposes and means of processing, rather than only the label in a contract. An agency is not automatically a processor for everything it does.

Where the UK GDPR applies and the agency processes personal data on the client's behalf, Article 28(3)(g) requires the processing contract to provide for deletion or return at the controller's choice after the processing services end, with an exception for legally required storage. Use the applicable agreement and privacy advice to resolve that obligation. It is not a universal right to the agency's methods, every third-party database or another member's account.

Document the return or deletion decision, any required retention and the people authorized to verify completion. Restrict retained records to their permitted purpose. Do not leave the exit open merely because the old provider's files are no longer visible to the client.

Relaunch only the work you can account for

The receiving team should be able to explain why each person is in its audience, what has already happened, what contact is permitted and who owns the next action. Use an organized prospect list to preserve that context. A new message draft can wait while an unresolved promise or restriction is checked.

If the old provider cannot supply a trustworthy state, leave those records on hold and work from the subset the client can verify. The cost of a smaller starting audience is visible. The cost of repeating an unwanted message or abandoning a promised answer arrives after the new engagement has already begun.