---
title: Lever Transfers
slug: lever-transfers
docTags: G8dmC6tNw9fak7qGrSH3Z,HnLaVwOXkGQqP1zfLQjeE
createdAt: 2025-07-10T09:54:58.322Z
---

:::hint{type="warning"}
This article is for Analytics customers using Lever as their ATS.
:::

Lever does not allow opportunities to be transferred between postings. To consider an opportunity for another job posting, create a new opportunity and add it to the new posting. We refer to this as transferring throughout this article.

To counteract the impact this has on reporting, we recommend:

- Creating an archive reason specifically for transfers (for example, "transferred to another job" or "considered for another job"). This is the easiest way to filter out duplicative data.
- Transferring opportunities earlier in the process to get as much of the data as possible on one opportunity.

The following data points are lost in the transfer:

- Sourced by user (and opportunity owner) can now only be the user who added the opportunity to the new job posting. This usually leads to inaccurate sourcing reporting.
- Interviews from the previous job still exist in the reporting but are not tied to the new opportunity.
- Time spent in stages is only linked to their respective opportunities. If an opportunity is incorrectly placed in a stage and then immediately moved to another stage, this skews the time spent in that stage lower.

# Impacted commonly used reports

## Passthrough rate reports

Passthrough rate tables report on the journeys of a group of opportunities through the stages/stage groups. Since they track each opportunity, a candidate who transferred to a new job is counted for both the old and new requisitions and is considered not to have passed the stage from which they were transferred. For this reason, we recommend filtering out by archive reason.

## Time to hire or time to offer

These may be inaccurate because the opportunity start date is the date the transfer occurred, which usually does not align with the application date. When a transfer occurs, you can set a different application date. You can also edit the application date after the transfer. We recommend updating the application date on the new opportunity.

## Time in process

To keep these reports as accurate as possible, ensure opportunities are added to the proper stage in the new requisition. Since the duration of each opportunity is accurate, you do not need to filter any data out. No change is needed here.

## Archive reason or conversion rate reports

Because ending an opportunity's consideration on the older requisition appears to be an archive or rejection, transfers may skew your archive reason and conversion rate data. We recommend filtering out by archive reason.

## General reporting

Remember for future reports that a candidate who was transferred has multiple opportunities and multiple consideration end dates. When building reports, consider if you want transfers to count as one or one per opportunity. Some situations where you may want to consider filtering out transfers by archive reason:

- Reports that report on an opportunity's consideration end date, archive date, etc.
- Reports selecting by archive reasons