Learn what happens to archived and hired applicants when you activate Pipeline View
When you activate Pipeline View, your account is migrated from the classic workflow to the new pipeline-based experience. As part of this migration, the migration wizard may automatically create additional inactive statuses to ensure existing applicant records remain accurate and retain their historical status information.
This article explains why you may see new inactive statuses after migration and how they help preserve your data.
Why are new inactive statuses being created?
In the previous hiring workflow, an applicant's status and their Hired or Archived state were managed separately.
This meant it was possible for an applicant to be:
- Marked as Hired using the Mark as Hired button while still having a status such as Offer Sent.
- Marked as Archived using the Archive button while still having a status such as Phone Interview.
- Left in a status that no longer reflects their final outcome.
With Pipeline View, these concepts are now connected. Applicants who have been marked as Hired or Archived are organized within the appropriate Hired or Archived stages while still retaining information about where they were in the hiring process.
To preserve this historical context during migration, the migration wizard may automatically create inactive statuses for applicants who were marked as Hired or Archived but whose status was never updated.
Example
Before migration:
| Applicant | Status | Applicant State |
|---|---|---|
| Jane Smith | Phone Interview | Archived |
After migration:
| Applicant | Status | Applicant State |
| Jane Smith | Archived - Phone Interview | Archived |
Rather than moving Jane into a generic Archived status, the system preserves the fact that she was archived while in the Phone Interview stage.
The same process applies to applicants who were marked as Hired. This ensures no historical information is lost and allows you to accurately understand where applicants were in your hiring process when they were hired or archived.
What if an applicant was both Hired and Archived?
If an applicant was marked as both Hired and Archived before migration, the Hired state takes precedence.
An applicant can only have one final state after migration:
- Hired, or
- Archived
Never both.
This ensures applicants retain the most meaningful outcome while preserving the status they were in at the time.