Lever → Ashby Recruiting API Migration Guide
This article covers how to initiate the API data migration from Lever to Ashby Recruiting, including how to configure the information needed to start the sync, what is imported and post-migration tasks.
If you are using Lever Basic and don't have access to generate Lever API credentials, review Historical Import MigrationsHistorical Import Migrations.
Permissions and prerequisites:
- You need to have Super Admin access in Lever with permissions to manage API credentials and manage integrations to generate an API key.
- You will need to be an Organization Admin to add the API key details in Ashby.
API key setup
Generate an API key
As a first step, create a Lever API key with read permissions enabled for all endpoints. To do this:
- Navigate to Settings > Integrations and API > API Credentials and click Generate New Key.
- Under the Permissions header, select Select all read permissions to grant read-only rights to all data.
- Toggle on Confidential data access to ensure the migration includes your team's confidential jobs and applications.
If you cannot enable confidential scopes, contact [email protected] or your Customer Success Manager (CSM). We can configure the migration to skip confidential data so everything else syncs correctly, but you need to add any confidential data manually.
- Scroll to the bottom of the page and click DONE. This is required to finalize the API key generation.
- Enter a name for your API key and click Generate key.
- Click the Copy Key button next to the API key (which can be found next to the 'Key name' field).
Lever's full guide on generating an API key can be found at Generating and using API credentials.
Add API key to Ashby
- Sign in to your Ashby account.
- Add the API key to the Lever API Key field in your Ashby Lever Settings.
Notify your Customer Success Manager (CSM) or Startup Customer Success Team when this is done, and we import your data.
Post-migration tasks
The following tasks should be completed once your migration from Lever is complete.
Map your Lever sources
First, you need to map any sources you want migrated to Ashby. To do so, follow these steps:
- Add any sources you want to migrate at Admin > Organization Setup > Source Types and SourcesCandidate Sources .
For more on configuring sources, check out Source Types and Sources.
- Map your sources from Lever to Ashby at Admin > Data Mapping > Lever Source Mapping.
- Click Apply to Applications… in the top right corner to apply them.
Setting up permissions in Ashby
We don't migrate user permissions from Lever, so you need to configure permissions for your users within Ashby. For more information on setting up users and user permissions check out User Permissions.
Disable Lever integrations
To complete the transition to Ashby, you need to ensure no new candidates are going into Lever moving forward. To accomplish this you should:
- Disable any job board integrations (e.g., LinkedIn) in Lever and enable the corresponding job board integrations in Ashby.
- Redirect your career page to your Ashby job board instead of your Lever job board.
- Close out your jobs in Lever (be sure your CSM has confirmed the sync is complete and off before taking this step).
After you complete these steps, proceed to Ashby Admin OnboardingAshby Admin Onboarding, but don't add any jobs, departments, etc. already in Lever, since these were migrated.
FAQ
What is migrated from Lever?
- Jobs and job postings
- The interview plan configured in Lever
- Candidates and their application details (resumes, applications, files, interviews, feedback, tags, notes, and referral information)
- Data retention dates are not migrated. More on this below.
- Offers (offer data and offer letters)
- Interview and feedback form templates
- Users (without permissions)
- EEOC data
- Teams, Departments, and Locations (based on their links to jobs)
- Archive Reasons
- Confidential data, including Application Forms, Job Postings, and Candidates, is migrated when your API key has Confidential data access enabled. Without this permission, the sync fails and skips any sections containing confidential data.
- Requisitions (Openings in Ashby — Requisition IDs are mapped to Opening IDs)
For Lever customers we cannot migrate:
- Email templates
- Historical email communication in the candidate's feed
- Nurture sequences
- User permissions
- Offer Letter Templates
- Profile Forms
- Candidate Location
- Candidate consent dates/data retention dates
You can import data retention dates via a CSV import to add this information to migrated candidates once the API migration is complete. More on this can be found at Data Privacy and ComplianceData Privacy and Compliance.
I have openings with multiple headcount attached to them. Can these be migrated?
We do not support directly migrating openings or requisitions from Lever that have multiple headcount. If you need further assistance, reach out to your CSM or the Support team.
Will something happen to feedback forms or other things we create in Ashby prior to the migration?
If you create an object in Ashby (e.g., a feedback form template), it remains unchanged by the migration. That said, the migration moves over the objects listed above, so we recommend completing the migration first to prevent duplicating effort.
I updated a candidate profile, but it changed back overnight. What's happening?
Letting your CSM know when they can disable the Applicant Tracking System (ATS) sync is a part of the migration process. Until that's completed, any changes you make to migrated data may be overridden.
Why are some migrated candidates named Unknown in Ashby?
If a candidate is anonymized in Lever, they are named Unknown in Ashby.
I'm seeing candidates that have migrated over from Lever with their source set as Unspecified. Why?
A source has not been applied to these candidates yet. Ensure that your sources are mapped appropriately via the Lever → Ashby Recruiting API Migration Guide steps above.