1. LandOffer
  2. Blog
  3. All articles
  4. Duplicate Handshake Accounts: Preserve Applications Before Requesting a Limited Merge

Job search

Duplicate Handshake Accounts: Preserve Applications Before Requesting a Limited Merge

Current official guidance and two completed fictional audits separate limited student merges from deletion, account views and institution changes.

9 min readLandOffer team

If you have two Handshake accounts, preserve the application history attached to each before requesting any cleanup. Handshake's current institutional guidance describes a limited, Support-assisted process for qualifying student accounts. It does not promise that every pair of accounts, every message, or every activity record can be combined.

Check whether you have duplicate student records, different account views, additional emails on one record, or separate institution connections. Those are different situations. Keep ongoing applications visible in your own records while the account question is unresolved; recent roles on LandOffer.ai provide another discovery route without requiring you to recreate Handshake history.

An editorial illustration shows two distinct student portfolios and a carefully selected application packet

Identify the two records before choosing a remedy

We reviewed current public Handshake Help Center guidance and an institutional alumni-access example on October 20, 2026. Direct HTTP requests to several Handshake help pages returned 403, while their public articles were readable in the native browser and official web results. We did not access a private account, change settings, request a merge, delete anything, contact Support, or test an application transfer.

Start by giving each suspected account a neutral private label, such as Account A and Account B. Record the associated email, institution connection, account type, and application activity you can actually identify. Do not decide which to keep from the most recent login alone. An apparently empty account may hold your career-center connection, while another holds your application history.

Handshake's connected-versus-unconnected explanation says some job search, applications, and public features exist without a school connection. Institution-specific jobs, services and activities have separate access conditions. An account that can search jobs therefore is not necessarily connected to the school you expect.

Begin by identifying the records and preserving the references you need. Making both profiles look identical, submitting replacement applications or creating a third account can make the history harder to interpret without resolving the original identity problem.

What the current limited-merge guidance actually covers

Handshake's September 22, 2026 guidance limits automatic merging to account creation; existing duplicates after sign-up need separate assessment.

For Support-assisted merging, the unconnected account must be pending/rejected for the institution, have accepted terms, confirmed email or authorized SSO, no block/disablement, and job applications. The institution-connected account must have accepted terms, no block/disablement, and qualifying history: attendance, appointments, experiences, applications, or First Destination Surveys.

The documented eligible transfer list is email address, applications, documents, profile photo, and custom profile link. The unconnected duplicate is removed. This is not a complete merge. For categories absent from that list, ask about handling rather than assuming transfer or loss. Support determines whether the particular pair qualifies.

Those conditions describe an institutional Support workflow, not a self-service Merge button for candidates. Keep the distinction between “these facts appear consistent with the published criteria” and “Support approved and completed this operation.” The latter needs an actual response and outcome, neither of which we obtained.

Worked preservation audit: reconcile applications before the request

Consider fictional graduate Amaya. Account A is associated with a school email and the expected career center. Account B uses a personal email and shows a pending connection. These are invented inputs for a preservation exercise, not records we viewed. Amaya can identify three application entries and has retained her own submitted document copies.

Her first rough note says, “Three applications; both accounts have my resume.” That is too vague to check later. The completed reconciliation makes each application recognizable after a later account change:

Fictional application record Where it appears before any request Preserved reference and follow-up
Northbank Labs, Backend Intern, posting N17 A only; applied October 8 Saved submission acknowledgement and the exact backend resume version
Harbor Metrics, Data Engineer, posting H42 B only; applied October 11 Saved application date, displayed status, and the data-focused resume copy
Northbank Labs, Platform Intern, posting N23 B only; applied October 14 Kept distinct from N17 despite the same employer name; follow-up date October 24

All organizations, identifiers, dates, and statuses in this example are fictional. The point is that three applications are not interchangeable with three employer names or three document files. Two applications to one employer remain two records because their posting identifiers and roles differ.

Amaya also records one resume file in each account. The filenames are both resume.pdf, but her retained copies have different content: the first emphasizes API work and the second emphasizes data pipelines. She labels each retained copy by role and submission date; the shared filename cannot identify which version accompanied H42 or N17.

Her completed preservation result is: three identifiable application references, two distinguishable document versions, and one current follow-up date. She has not downloaded an official account archive or proven that all platform data is recoverable. She has simply preserved the material needed to recognize these applications later.

Two other items remain outside that result: an employer conversation in B and a career-center appointment in A. She notes their existence privately and asks how each will be handled. She does not treat either item as covered merely because applications may be eligible for transfer.

Amaya orders her references by application identifier rather than by account age. That lets her check a later outcome without assuming the oldest profile is the most important one. For N23, the follow-up date stays October 24 even while the account question is open; a support issue does not automatically change an employer's interview or document deadline.

Her private record also separates a saved acknowledgement from a live status. The acknowledgement establishes the historical submission in this fictional case; it does not prove that the employer still considers the application active. If the displayed status later changes, she records that change alongside the original date instead of replacing the history with a single new label. None of those notes requires creating another application.

The audit changes her proposed request. Instead of “Delete my old account,” her private brief says: “Please assess these two student records; B contains H42 and N23, and A contains N17. I need the handling of these applications and the two document versions clarified before any removal.” This is an unsent, fictional brief, not a support message we delivered.

Why deletion is a separate decision

Handshake's student-deletion guidance states that deletion is permanent and unrecoverable, historical activity can block it, and institutional student-sync records need coordination so an account is not recreated. Career services staff need the specified permission for unaffiliated accounts. Students use the Support request route rather than these staff controls.

A blocked Delete action is therefore not proof that the account is useless, broken, or ready for a workaround. It may be protecting activity that needs review. Likewise, a genuinely unused duplicate and an active account with applications should not receive the same instruction merely because both are labeled duplicate.

An independently saved resume is not a replacement for an application receipt. It cannot establish the posting, submission date, employer status, or conversation attached to that account. Preserve the relationships between records, not just the latest file in a downloads folder.

Worked classification audit: three similar-looking problems

Now consider a second fictional case, Theo, who has collected three observations while preparing for alumni access. The completed audit separates what each observation establishes from the action it does not justify. No real login or institution request was performed.

Fictional observation Completed classification Decision recorded before contacting anyone
One email opens both Student and Employer views A role/view question, not evidence of two duplicate student histories Identify the Student view containing applications; do not request removal of the Employer role as a merge shortcut
A personal email cannot be added because it is already associated with another record An ownership/conflict question; the second record's type is still unknown Record the exact error and ask the official support route to identify the relevant account situation
An older university login and a current university login show different institution connections A cross-institution question, not an assumed eligible duplicate pair Ask the current career center which institutional workflow applies; retain both histories pending clarification

The first row follows Handshake's Switching User Views guidance: confirmed accounts of different types using the same email can support switching. Different addresses are not linked for that switching feature. Switching a view is not evidence of a student-history merge.

For the last row, the cross-institution guidance describes institution-dependent routes. In a different-school email-domain case it describes separate school accounts; in other specified cases it describes confirming a switch and involving Support. It does not supply a universal instruction to consolidate all former and current school records.

Theo's final private decision is to resolve the unknown account type and school relationship before selecting a merge path. He keeps a short list of the two application histories and the access he wants to preserve. He does not label the unexplained email conflict “safe to delete,” and he does not assume a current-school approval will carry old-school appointments across.

This completed audit produces three different classifications from superficially similar symptoms. It is deliberately not a promise that Support will merge, switch, restore, or approve any of these fictional records.

An editorial illustration distinguishes role views, email ownership, and separate institutional records

Preserve future access without creating another duplicate

Handshake's primary-email instructions allow multiple associated addresses but require an unused address and confirmation of the new inbox. The added address remains pending until confirmed; the published confirmation window is seven days. A confirmed address can be made primary for communications. Changing primary email does not itself change a school's SSO login method.

For an institutional example, Tufts' student and alumni guidance tells graduates to add a personal address before their school email expires and to contact its career center before creating a new account if access has already expired. That is Tufts-specific advice, not a universal alumni entitlement or expiry schedule for every school.

The practical distinction is between communication continuity and authentication continuity. A reachable inbox matters for notices and verification, while your actual login route may depend on the school. Record both questions separately when seeking help. Do not assume that setting a primary email resolves an inaccessible institutional identity.

This article concerns student job-search accounts. Handshake AI's good-standing guidance separately warns against creating another account to work around profile, verification, or access problems. A student-account merge description should not be extended into a promise about AI-project verification, earnings, or work access.

What to verify after an actual resolution

When an authorized institution or Support process finishes, compare the resulting account with your original inventory. Identify the retained account, the intended application entries, relevant document versions, reachable email, and institution connection. Ask separately about any missing history. A general “resolved” message is not a substitute for checking the records that mattered to you.

If only some questions are answered, keep the rest open in the same incident record. Avoid submitting duplicate applications simply to recreate a missing visual entry: that could create a different employer-side problem. Nothing in this article establishes recovery guarantees, a Support response time, or an automatic reversal of an approved operation.

Once you have a clear record of the account situation and remaining follow-ups, continue discovering recent roles on LandOffer.ai. Keep each new application tied to its employer and role while tracking the unresolved Handshake records separately.

Sources and Further Reading