Lever → Ashby Recruiting API Migration Guide

follow this guide to initiate the api data migration from lever to ashby recruiting if you are using lever basic and don’t have access to generate lever api credentials, please review docid\ ag2ad1x27eiycjhxycrvh api key setup generate an api key as a first step, create a lever api key with read permissions enabled for all endpoints the https //t sidekickopen87 com/s3t/c/5/f18dqhb0s7kf8cvq7cv737b159hl3kw7 k2841cx6ngw35qnwb7vbmm2vs7 5r4jjn7hf197v5y04?te=w3r5hfj4cm2zww3q 1qy1jcfkxw3k8k1p43nnm1w1lwwgd4hltfjw49rljn3zvdqgw1v2qxw1w jpww1x079c1glld5w1gznvm2hnnsjw3k1m5b1gy7mlw2nty6k3xwjrvw4mcw 01gy6qbw3k9dy74flg3yw43tc4k3h4s mw3sxxpm3h3bck1s3\&si=8000000017570661\&pi=df6336d8 b6f3 4835 efd4 78130d023525 explains this, but in short generate a new key select " select all read " permissions to grant read only rights to all data under the permissions header toggle on “ confidential data access" to ensure your team’s confidential jobs and applications are migrated scroll to the bottom of the page and click "done " note this is required to finalize the api key generation add in a name for your api key and generate the key please ensure your api key has confidential data access enabled to ensure no confidential data is lost if this is missed, this data may need to be recovered by your team manually later add api key to ashby go to https //app ashbyhq com/ and sign in add the api key to your https //t sidekickopen87 com/s3t/c/5/f18dqhb0s7kf8cvq7cv737b159hl3kw7 k2841cx6ngw35qnwb7vbmm2vs7 5r4jjn7hf197v5y04?te=w3r5hfj4cm2zww3zfpsj3zh1bdw4rybcs3fbt5sw3z8pwd41prypw4fgbqv3zhs7sw41y26c3kbsmy0\&si=8000000017570661\&pi=df6336d8 b6f3 4835 efd4 78130d023525 let your customer success manager or startup customer success team know when this is done and we'll import your data post migration tasks map your lever sources first, you’ll need to map any sources you’d like migrated to ashby to do so, follow these steps add any sources you’d like to migrate https //app ashbyhq com/admin/organizational settings/sources ( ) map your sources from lever to ashby here in admin https //app ashbyhq com/admin/data mapping/lever source mapping hit the apply to applications… button on the top right corner to apply them setting up permissions in ashby we don’t migrate user permissions from lever, so you’ll need to configure permissions for your users use the setup disable lever integrations to complete the transition to ashby, you’ll need to ensure no new candidates are going into lever to accomplish this you should disable any job board integrations (e g linkedin) in lever and enable the corresponding job board integrations in ashby ( https //help lever co/hc/en us/categories/360002628931 integrations api ) redirect your career page to your ashby job board instead of your lever job board close jobs in lever after you’ve completed these steps, please proceed to , 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 all of their details (resumes, applications, files, interviews, feedback, tags, notes, referral information, etc ) offers (offer data and offer letters) interview and feedback form templates users (without permissions) eeoc data teams, departments and locations (based on them being linked to jobs) archive reasons confidential jobs (please ensure that your api key is created with the permissions to access confidential data and confirm you’d like this data migrated with the startup success team or your csm prior to the sync) 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 w ill 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 , feedback form template), it will remain unchanged by the migration that said, the migration will move over the objects listed above, so we recommend completing the migration first to prevent duplicating effort h elp! i updated a candidate profile, but it changed back overnight! letting your csm know when they can disable the 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'll be named unknown in ashby i'm seeing a lot of candidates that have migrated over from lever with their source set as unspecified why? docid\ ybylw cykxhr0pvykx5rk make sure to click the apply to applications button to ensure that sources are applied