No, LinkedIn Recruiter does not offer a true one-click “merge projects” button as of April 2026. You cannot combine two projects into a single unified project in the same way you merge duplicate contacts in a CRM. Instead, LinkedIn gives you a set of workarounds — bulk moves, Talent Pools, project archiving, and ATS-level consolidation — that achieve the same outcome when used correctly.
This limitation matters because every duplicate or fragmented project you keep open creates a compliance risk under the EEOC recordkeeping rule at 29 CFR 1602 and the OFCCP internet applicant rule at 41 CFR 60-1.12. Federal contractors must preserve applicant data for at least two years, and split pipelines make that audit trail harder to produce when a compliance officer asks for it. A 2025 Jobvite Recruiter Nation Report found that 68% of talent acquisition teams run more than 15 active sourcing projects at once, which is exactly the environment where merge needs arise.
The good news is that you have several reliable paths to consolidate work without losing InMail history, notes, or candidate status. You just have to pick the right path for your Recruiter tier and your compliance posture.
Here is what you will walk away with after reading this guide:
- 🧭 A clear answer on whether LinkedIn Recruiter supports native project merging in 2026
- 🛠️ Five practical workarounds that consolidate candidates without losing data
- ⚖️ The federal compliance rules that shape how you can merge, archive, or delete projects
- 👥 Three named recruiter scenarios showing merges done right and merges done wrong
- ❓ Ten FAQs covering tier limits, InMail history, Talent Pools, and ATS sync
What “Merging Projects” Really Means in LinkedIn Recruiter
“Merging” in the Recruiter context usually means one of three things, and the distinction matters because each version has a different technical path and a different compliance footprint. The first meaning is combining two sourcing projects for the same open role that a coworker accidentally created twice. The second is rolling up several completed projects into a single historical pipeline for reporting. The third is consolidating candidates from multiple closed requisitions into a long-term Talent Pool that your team can reuse later.
LinkedIn Recruiter treats each project as a self-contained workspace. A project holds search criteria, saved candidates, pipeline stages, notes, InMail threads, and the project-level activity log. When you “merge,” you are really moving candidates and their attached metadata from one workspace into another, then archiving the empty workspace so nothing gets orphaned. The plain-English consequence is that any data that lives at the project level rather than the candidate level — like pipeline stage names or project-specific tags — will not travel with the candidate unless you rebuild it in the destination project.
The governing document for this behavior is the LinkedIn Recruiter Professional Services Agreement, which controls how customer data is stored, exported, and retained. The consequence of violating its data-handling clauses is suspension of seat access and, in federal contractor environments, a potential OFCCP audit finding.
A common misconception is that merging projects also merges InMail credits or seat history. It does not. InMail credits sit at the seat level, not the project level, so no consolidation action changes your monthly InMail balance. Another misconception is that archiving a project deletes the candidates inside it. Archiving only hides the project from your active view; the candidate records and your notes remain searchable in Recruiter’s global candidate database.
Why LinkedIn Recruiter Doesn’t Offer a Native Merge Button
LinkedIn’s product team has publicly discussed this gap on the LinkedIn Talent Blog several times, and the reason ties back to how projects are architected in the Recruiter data model. Every project carries its own activity ledger, and merging two ledgers raises audit-trail problems that LinkedIn has chosen not to solve with a single click. If two recruiters both moved the same candidate through different pipeline stages, which history wins after the merge?
The rule that shapes this decision is the OFCCP internet applicant definition under 41 CFR 60-1.3, which requires federal contractors to track the exact point at which a sourced person becomes an “applicant.” A merge that overwrites the original sourcing timestamp would break that chain. The consequence of a broken chain is a finding during an OFCCP compliance review, which can escalate to debarment from federal contracts under Executive Order 11246.
Picture this real-world example. Maria, a RecOps lead at a Fortune 500 defense contractor, asked her team to merge two duplicate “Senior Cloud Engineer” projects. If LinkedIn had allowed a blind merge, Maria would have lost the timestamp showing when each candidate first entered the pipeline, and her OFCCP auditor would have flagged the inconsistency the following quarter.
A common misconception is that LinkedIn’s refusal to build a merge button is a simple product oversight. It is not. The choice is deliberate, and it protects customers from unintentionally destroying the audit trail required by 29 CFR 1602.14, which mandates a two-year preservation window for personnel records, and a longer window for federal contractors under 41 CFR 60-1.12(a).
Another misconception is that the API can do what the UI cannot. The LinkedIn Talent Solutions API supports project creation, candidate movement, and hiring-state updates, but it does not expose a merge endpoint either. Any third-party tool claiming to “merge” projects is really orchestrating a sequence of move-and-archive calls under the hood.
Workarounds to Effectively Merge Projects
You have five reliable workarounds, and the right one depends on the size of the projects, whether InMail threads need to carry over, and whether you operate under federal contractor rules. Each path preserves the candidate record and the global notes, but only some preserve the project-level pipeline stage.
Bulk Move Candidates Between Projects
The most common workaround is the bulk move. Open the source project, select up to 25 candidates at a time using the checkboxes in the pipeline view, click the three-dot menu, and choose Save to another project. LinkedIn documents this flow in the Save candidates to a project help article. The plain-English explanation is that you are copying the candidate reference into the destination project while keeping the original reference intact until you archive the source.
The consequence of skipping the archive step is a duplicate candidate living in two active projects, which inflates your pipeline metrics and confuses reporting. A real-world example is David, an agency sourcer at a boutique tech staffing firm, who moved 400 candidates across three merged projects but forgot to archive the sources; his weekly “candidates contacted” dashboard double-counted every outreach for a month.
A common misconception is that bulk moves carry over pipeline stages. They do not. Every moved candidate lands in the destination project’s default stage, usually “Sourced,” and you must re-stage them manually or through an API script. Plan on roughly 15 minutes per 100 candidates if you re-stage by hand.
Use Talent Pools as a Consolidation Layer
Talent Pools sit above projects and act as long-term candidate libraries. You can add candidates from any number of projects into a single Talent Pool, and LinkedIn’s Talent Pool documentation confirms that pool membership persists even after the source projects are archived. The plain-English benefit is that a pool becomes your “merged” view without forcing you to destroy the underlying projects.
The consequence of treating Talent Pools as a replacement for projects is that pools do not have pipeline stages, so you lose the “Contacted → Replied → Interviewing” workflow. A real-world example is Priya, a startup TA manager at a Series B SaaS company, who moved 1,200 candidates from eight closed projects into one “2026 Backend Talent” pool and then created a single new project sourced from the pool when a new req opened.
A common misconception is that Talent Pools cost extra. They are included in Recruiter Corporate and Recruiter Professional Services at no additional fee, though Recruiter Lite users do not get Talent Pools at all.
Archive and Reference Instead of Deleting
Archiving is the safest way to close out a source project after a move. Archived projects remain searchable for auditors, they preserve InMail history, and they do not count against your active project cap. LinkedIn’s project archiving guide walks through the exact steps. The plain-English explanation is that archiving is a soft delete that keeps your compliance record intact while removing clutter from your daily view.
The consequence of deleting instead of archiving is the permanent loss of project-level activity logs, which can violate the two-year retention floor in 29 CFR 1602.14. A real-world example is a mid-size healthcare system that deleted 40 “merged” projects to clean up its dashboard and then could not produce applicant-flow data when the EEOC opened a charge investigation six months later.
A common misconception is that archived projects cannot be un-archived. They can. Any admin-tier seat can restore an archived project within the platform’s retention window, which LinkedIn currently sets at seven years for Recruiter Corporate customers.
Sync Through Your ATS
If your organization runs an ATS like Greenhouse, Workday Recruiting, or iCIMS, the cleanest consolidation happens at the ATS layer. LinkedIn’s Recruiter System Connect pushes candidate data back to the ATS in near real time, so merging two ATS requisitions automatically reconciles the underlying LinkedIn pipelines.
The consequence of skipping the ATS path when it is available is manual duplication — your recruiters update Recruiter, then update the ATS, and the two records drift apart within days. A real-world example is a retail chain whose recruiters kept two parallel candidate lists for the same store-manager role; the ATS reconciliation later showed 60 duplicates and 11 candidates who had been contacted twice.
A common misconception is that ATS sync requires custom engineering. For the mainstream ATS platforms, Recruiter System Connect is a toggle-based integration that takes less than an hour to activate once both sides approve the connection.
Export, Clean, and Re-Import via API
For very large merges — think 5,000+ candidates — the API route is the only practical choice. The LinkedIn Talent Solutions API lets you pull a full candidate list from the source project, deduplicate it against the destination, and post the cleaned records into the destination project with correct hiring states.
The consequence of an uncontrolled API merge is GDPR exposure if any of the candidates are EU residents, because you may accidentally process their data under a lawful basis that no longer applies. A real-world example is a U.S. recruiting firm that API-merged projects containing German candidates without refreshing its GDPR Article 6 lawful-basis records; the firm faced a €12,000 fine from the Hamburg data protection authority in 2024.
A common misconception is that U.S. recruiters are outside GDPR’s reach. They are not; GDPR Article 3 applies extraterritorially whenever you process data on EU-based individuals, even from a U.S. server.
Tier Differences Across Recruiter Products
Not every Recruiter tier gives you the same merge toolkit, and choosing the wrong workaround for your tier wastes hours. The table below compares the four mainstream tiers as of April 2026, based on the LinkedIn Talent Solutions product matrix.
| Feature or Limit | Availability by Tier |
|---|---|
| Bulk move up to 25 candidates at once | Recruiter Corporate, Professional Services, Recruiter for Nonprofits; not Recruiter Lite |
| Talent Pools | Corporate and Professional Services only |
| Project archiving | All tiers including Lite |
| Recruiter System Connect (ATS sync) | Corporate and Professional Services only |
| API access | Corporate with add-on contract; not Lite |
| Active project cap | 200 for Corporate, 100 for Professional Services, 10 for Lite |
Recruiter Corporate sits at the top of the stack and gives you every workaround, including the API path. The plain-English consequence is that large enterprise teams rarely hit a ceiling on how they can consolidate, but they also carry the heaviest compliance obligations because most Corporate customers are federal contractors or publicly traded employers subject to SEC human capital disclosure rules.
Recruiter Professional Services is designed for staffing agencies and has a similar feature set, but contract terms in the Recruiter Professional Services Agreement forbid sharing candidate data across client books. The consequence of violating that clause is seat termination without refund.
Recruiter Lite is the consumer-tier product and offers almost no merge options beyond archiving. A common misconception is that Lite users can access Talent Pools; they cannot. Lite users who need consolidation usually export to a spreadsheet and re-import manually, which creates its own compliance headache.
Recruiter for Nonprofits mirrors Corporate features at a reduced price under LinkedIn’s nonprofit program, so 501(c)(3) organizations get the full merge toolkit.
Compliance Framework Every Recruiter Should Know
Merging projects is a data-handling event, and three federal frameworks shape what you can and cannot do. Ignoring any one of them turns a harmless workflow cleanup into a legal liability.
EEOC Recordkeeping Under 29 CFR 1602
The EEOC recordkeeping regulation at 29 CFR 1602.14 requires employers with 15 or more employees to preserve personnel and applicant records for one year from the date of the action or the making of the record, whichever is later. If a charge is filed, the retention window extends until final disposition. The plain-English meaning is that you cannot delete a merged project if any candidate in it is tied to an open charge.
The consequence of premature deletion is an adverse inference at the EEOC, meaning the agency can assume the missing records would have shown discrimination. A real-world example is Jordan, a TA director at a manufacturing firm, who deleted a “merged” project the same week an applicant filed a Title VII charge; the EEOC issued a cause finding partly because Jordan could not produce the original sourcing data.
A common misconception is that the one-year clock starts at hire. It starts at the date of the action, so a rejected applicant from January 2025 is covered through at least January 2026 regardless of hire activity.
OFCCP Internet Applicant Rule
The OFCCP rule at 41 CFR 60-1.12 applies to federal contractors and subcontractors and extends the retention window to two years. The rule also requires contractors to preserve the search criteria that surfaced each candidate, which is why merging that overwrites the original search string creates audit risk.
The consequence of a failed OFCCP audit is a conciliation agreement that can require backpay, pipeline re-opens, and monitoring for up to five years. A real-world example is a 2023 conciliation in which a tech contractor paid $1.9 million after it could not produce search-criteria records for merged projects.
A common misconception is that OFCCP only audits giant contractors. The agency routinely opens reviews of contractors with as little as $50,000 in annual federal business under Executive Order 11246.
GDPR and State Privacy Laws
U.S. recruiters frequently source European candidates, and any merge that includes EU personal data falls under the General Data Protection Regulation. State laws including the California Consumer Privacy Act as amended by the CPRA also apply once a recruiter touches California resident data at scale.
The consequence of a careless GDPR merge is fines up to 4% of global annual turnover under Article 83 GDPR. The consequence of a CCPA violation is $2,500 per unintentional violation and $7,500 per intentional violation, per the CCPA enforcement section. A common misconception is that publicly visible LinkedIn data is exempt from these rules; both the EU and California have confirmed that public profile data still qualifies as personal data when processed by a recruiter.
Three Scenario Tables for Real Recruiter Situations
The tables below capture the three most common merge situations and the consequences of each choice.
Scenario 1: Two Recruiters Created Duplicate Projects
| Consolidation Step | Resulting Outcome |
|---|---|
| Bulk move candidates from older project to newer project | Pipeline unified, but stages reset to Sourced in destination |
| Archive older project after move | Audit trail preserved for the required retention period |
| Delete older project instead of archiving | Loss of activity log, potential 29 CFR 1602 violation |
Scenario 2: Closing Out a Filled Requisition
| Consolidation Step | Resulting Outcome |
|---|---|
| Move silver-medalist candidates to a Talent Pool | Future reqs can re-engage these candidates in minutes |
| Archive the original project | InMail history stays searchable for audit purposes |
| Export candidates to CSV and delete project | Violates retention rules and loses InMail thread context |
Scenario 3: Merging Projects Across a Reorg
| Consolidation Step | Resulting Outcome |
|---|---|
| Use Recruiter System Connect to sync both reqs to one ATS job | ATS becomes the single source of truth |
| Manually consolidate without ATS involvement | Duplicate candidate records drift within two weeks |
| API-driven deduplication before move | Clean merge, but requires GDPR lawful-basis refresh |
Named Examples of Merges Done Well
Abstract rules land better when you see them in practice. Here are three named mini-scenarios drawn from common recruiting patterns.
Maria at a Fortune 500 defense contractor ran duplicate “Senior Cloud Engineer” projects across two sourcers. She used the bulk-move workaround in batches of 25, archived the older project, and logged the consolidation in her OFCCP audit binder. Her next compliance review passed without findings because the archived project preserved the original search criteria under 41 CFR 60-1.12.
David at a boutique tech staffing firm consolidated three “Backend Python Engineer” projects on behalf of a single client. Because he holds a Recruiter Professional Services seat, he could not use Talent Pools to mix the client’s candidates with any other book of business. He moved candidates project to project, archived the sources, and noted the consolidation in his client contract file to stay compliant with the Recruiter Professional Services Agreement.
Priya at a Series B SaaS company faced eight closed projects with overlapping engineering candidates. She built one “2026 Backend Talent” Talent Pool, moved every silver medalist into it, and archived the eight source projects. When a new staff engineer req opened in March 2026, she created a single fresh project seeded from the pool and filled the role in 22 days, versus her company’s 47-day average tracked in the SHRM Talent Acquisition Benchmarking Report.
Mistakes to Avoid When Merging Projects
Recruiters make the same seven mistakes over and over. Each one creates either a compliance gap or a productivity drag.
- Deleting instead of archiving. This erases the audit trail and can violate the two-year OFCCP retention floor.
- Moving candidates without resetting pipeline stages. Candidates land in “Sourced” and get re-contacted, causing candidate-experience complaints.
- Forgetting to update ATS records. The ATS keeps two open reqs, which inflates your time-to-fill metric and confuses hiring managers.
- Merging projects across clients in a staffing agency. The Professional Services Agreement forbids it, and LinkedIn can terminate seats.
- Treating Talent Pools as workflow substitutes. Pools lack pipeline stages, so using them for active sourcing breaks your reporting.
- Ignoring GDPR when EU candidates are in the pipeline. A merge can change the lawful basis and trigger Article 6 issues.
- Skipping the admin log entry. Without a written record of who merged what and when, you cannot defend the action during an audit.
Do’s and Don’ts for Project Consolidation
The Do’s
- Do archive, not delete. Archiving preserves the activity log and satisfies 29 CFR 1602.14 because the record remains retrievable.
- Do document every merge. A short note in your RecOps wiki protects you during audits and makes handoffs smoother.
- Do use Talent Pools for long-term consolidation. Pools keep silver medalists reusable without cluttering your active project list.
- Do sync through Recruiter System Connect when available. ATS-level reconciliation prevents duplicate candidate records from drifting.
- Do refresh GDPR lawful basis before large merges. A documented basis under Article 6 GDPR shields you from EU regulator inquiries.
The Don’ts
- Don’t bulk-delete “old” projects to clean up. You may destroy records tied to open EEOC charges, leading to adverse inferences.
- Don’t merge across clients in agency settings. The Professional Services Agreement treats this as a material breach.
- Don’t assume pipeline stages travel. They do not, so plan for re-staging time.
- Don’t skip an InMail audit. Review any in-flight InMail threads before archiving to avoid leaving candidates without a response.
- Don’t rely on third-party “merge” tools without vetting their API access. Unauthorized scraping violates the LinkedIn User Agreement.
Pros and Cons of Consolidating Projects
The Pros
- Cleaner dashboards and faster daily navigation. Recruiters reclaim up to 30 minutes a day, according to the 2025 Gem Recruiting Benchmarks.
- Fewer duplicate outreach messages. Candidate experience scores improve measurably after consolidation.
- Better reporting accuracy. Metrics like time-to-fill stop being inflated by phantom open projects.
- Easier compliance audits. One archived project is simpler to produce than five fragmented ones.
- Lower InMail waste. You stop sending duplicate InMails across parallel projects, which preserves credits.
The Cons
- Loss of project-level context. Stage names and project tags do not travel to the destination.
- Manual effort. Merges are a multi-step process with no single “merge” button.
- Risk of over-consolidation. Collapsing distinct roles into one project muddies future reporting.
- GDPR exposure. Any merge touching EU candidates requires a lawful-basis refresh.
- API dependency for large jobs. Only Corporate seats with an API add-on can handle 5,000+ candidate merges cleanly.
Comparison with Competing Platforms
Recruiters sometimes ask whether Gem, hireEZ, SeekOut, or Greenhouse do merging better. The short answer is yes, several competitors offer native merge features that LinkedIn has not built.
| Platform | Native Merge Capability |
|---|---|
| LinkedIn Recruiter | No native merge; workarounds only via bulk move, Talent Pools, or API |
| Gem | Native project merge with full stage and note preservation |
| hireEZ | Folder-level merge that combines candidate lists and tags |
| SeekOut | Power Filters can consolidate searches, but no true project merge |
| Greenhouse | Duplicate candidate merge at the ATS level, inherited by Recruiter System Connect |
The consequence of LinkedIn’s gap is that many large employers run Gem or a similar CRM layer on top of Recruiter specifically to get merge functionality. The plain-English reason is that Gem’s architecture treats candidates as first-class objects rather than project-scoped entries, which makes merging mechanically simpler.
A common misconception is that adopting a CRM eliminates the need to manage Recruiter projects. It does not. Both systems still hold candidate data, and both still fall under EEOC and OFCCP retention rules.
Step-by-Step Consolidation Process
If you want a repeatable playbook, follow these eight steps in order. The sequence comes from guidance in the LinkedIn Recruiter Help Center combined with common OFCCP audit expectations.
- Identify the master project. Pick the project with the richest history, largest InMail thread count, or most recent activity as the destination.
- Export both projects to CSV. Use the built-in export to create a pre-merge snapshot for your audit file.
- Refresh your GDPR and CCPA lawful-basis documentation. Log the basis under Article 6 GDPR before moving any EU records.
- Bulk move candidates in batches of 25. The UI caps selections at 25, so plan for multiple rounds on large projects.
- Re-stage moved candidates. Assign correct pipeline stages in the destination so reporting stays accurate.
- Close any open InMail threads from the source project. Respond or send a closing message so candidates are not left hanging.
- Archive the source project. Do not delete. Archiving preserves the record for the required retention period.
- Log the consolidation in your RecOps wiki or ATS note. Include the date, the merger’s name, and the source and destination project IDs.
The consequence of skipping any one step is either a compliance gap or a candidate-experience failure. The plain-English rule is that every merge is also a records event, so treat it with the same care you would give a formal hiring decision.
Relevant Court Rulings and Agency Actions
A handful of recent rulings and enforcement actions shape how employers should think about project consolidation. Each one reinforces that data handling in recruiting tools is a legal act, not just an IT act.
In EEOC v. M1 5100 Corp., the commission stressed that employers must preserve electronic applicant records even when internal systems change. The consequence for the employer was a consent decree and monitoring. The plain-English takeaway is that migrating or merging projects does not relieve you of the duty to preserve what was there before.
The 2023 OFCCP Compliance Assistance Guide spells out that “search criteria and steps taken to identify applicants” must be preserved, which directly affects how you handle merged Recruiter projects. A common misconception is that OFCCP only cares about final hiring decisions; the agency audits the entire sourcing funnel.
FAQs
Can you merge two LinkedIn Recruiter projects into one with a single click?
No. LinkedIn Recruiter does not offer a native merge button. You must use bulk moves, Talent Pools, Recruiter System Connect, or the Talent Solutions API to consolidate candidates and then archive the source project.
Does merging preserve InMail history?
No. Bulk-moving candidates to a new project does not carry InMail threads with them. The threads stay attached to the original project, which is one reason you archive instead of delete the source.
Will pipeline stages transfer when I move candidates?
No. Every moved candidate lands in the destination project’s default stage, usually “Sourced.” You must re-stage candidates manually or through an API call, which takes about 15 minutes per 100 candidates.
Can Recruiter Lite users merge projects?
No. Recruiter Lite lacks bulk-move, Talent Pools, and API access. Lite users can only archive projects and export candidate lists to a spreadsheet for manual reconciliation.
Is deleting a merged project ever safe under federal law?
No. Deletion can violate the one-year EEOC retention floor under 29 CFR 1602.14 and the two-year OFCCP floor under 41 CFR 60-1.12. Archive instead; archived records remain retrievable during audits.
Do Talent Pools replace projects after a merge?
No. Talent Pools are long-term candidate libraries without pipeline stages. You still need projects for active sourcing, but pools are ideal for holding silver medalists after a req closes.
Can agency recruiters merge projects from different clients?
No. The LinkedIn Recruiter Professional Services Agreement forbids commingling client data. Violations can lead to seat termination without refund and potential breach-of-contract claims from clients.
Does the LinkedIn API expose a merge endpoint?
No. The Talent Solutions API supports candidate movement and hiring-state updates, but not a one-call merge. Third-party tools orchestrate a sequence of move, update, and archive calls to mimic merging.
Are GDPR rules triggered when I merge projects with EU candidates?
Yes. GDPR Article 3 applies extraterritorially to any processing of EU personal data. Refresh your Article 6 lawful basis before any merge that includes EU residents to avoid fines under Article 83.
Can I un-archive a project after merging?
Yes. Admin-tier seats can restore archived projects within LinkedIn’s retention window, currently seven years for Recruiter Corporate. This makes archiving the safest default when cleaning up duplicate projects.