Historical Import Migrations

follow this guide to import your historical data from your previous ats into ashby import overview file based migrations are a two step process importing active candidates and job considerations so they can be added to open jobs importing historical data for your records and reporting purposes below, you will find a table listing the supported ats options for which we can run a file based migration and where you can submit a request to export your data legacy ats supported data lever https //help lever co/hc/en us/requests/ icims https //careers icims com/customer team team tailor https //www teamtailor com/en/contact/ smartrecruiters https //www smartrecruiters com/about us/contact us/ workable https //help workable com/hc/en us/requests/new jobvite https //help jobvite com/hc/en us/requests/ comeet https //help comeet co/ pinpoint https //www pinpointhq com/contact/ paycor https //www paycor com/services support/ homerun https //help homerun co/en/ gem ats reach out to your csm at gem or gem's support team for assistance importing active candidates if you have open roles in your previous ats with active candidates, we would recommend setting up the departments, teams and jobs you’re actively hiring for manually in ashby so you can continue hiring activities with minimal downtime for more information on creating jobs, check out docid\ l nciszrb9ztdr4u3idzr once you’ve set up these jobs in ashby, you can import your active candidate data using the csv import tool more on this at docid\ sorncj66lghrflracxetj exporting historical data to import historical data, you will need to export your data from your previous ats once you’ve received your exported data from your previous ats, your csm or onboarding team will send you a link via sendsafely so you can upload your exported files importing historical data into ashby once we’ve received your files, our engineering team will get to work on the import we import the following data legacy ats supported data lever • historical jobs • candidates • applications • resumes • users • notes • interview feedback • interview stages icims job (optional) • title • external req id candidate • name • email • linkedin • phone number • added at date • source • credited to • resume • user selected custom fields application • submitted at • last activity • source • credited to • recruiter • archive reason • interview stage (mapped to lead, active, hired, or archived) offer • offer status • created at • decided at • offer custom fields forms selected forms will be imported as candidate notes the note's created at date will be the date of submission, so they should show chronologically in the feed the author of the note will be the submitter of the form (if they exist as a user in ashby) interviews a record of the interview, all meetings of the interview with times and attendees will be imported as a candidate note the note's created at date will be of the time of the first meeting in the interview, so they should show chronologically in the feed teamtailor we import the following data • candidates ◦ name, email, phone, social links, tags, source ◦ notes, feedback (imported as notes) candidates will be matched against existing candidate profiles (based on email address) if a matching candidate profile isn’t found, a new candidate will be created • applications (added to ashby as job considerations) existing applications will be searched for when importing applications if an existing job consideration isn’t found in ashby a new one is created if a new job consideration is created, it will be added to one of the following stages of the job’s interview plan lead, application review, hired, archived if an existing application already exists, it will not be updated with the historic information (in the case of the candidate’s application being moved forward in ashby, rendering the imported information obsolete) • jobs (optional) jobs will be matched against the job titles of existing jobs before creating a new one if a new job is created, then they will follow the default interview plan on your ashby account as far as team and location go, they will be added to the job if a match is found when importing if no match is found, a generic location and team is used if jobs are not imported, then applications will be imported to a generic job we will not import the following • job postings • interview plans • openings smartrecruiters what do we import? • jobs • users • candidates ◦ name, email, phone, location ◦ notes, feedback (imported as notes) • applications (with rejection reasons) ◦ stages are mapped to default interview plan stages5 what don't we import? • candidate sources • files • resumes additional information • stages will be mapped to matching default interview plan stage • feedback will be added as notes on the candidate profile workable we will import the following • jobs • candidates (including tags if these are in the candidate csv file) interview stages for candidates aren’t mapped due to lack of data provided from workable therefore we import candidates into the following stages application review, hired, or archived • applications • messages and comments (these are added as notes in ashby) • ratings (these are mapped as scorecards in ashby) • resumes jobvite • jobs • candidates ◦ name, email, resume, offers, phone, location • applications • notes • feedback what don't we import? •candidate sources comeet we import the following • candidates (including feedback listed as a note, notes, tags, resume, email, phone, social links and source) candidates will be matched against existing candidate profiles (based on email address) if a matching candidate profile isn’t found, a new candidate will be created • applications (added to ashby as job considerations) existing applications will be searched for when importing applications if an existing job consideration isn’t found in ashby a new one is created if a new job consideration is created, it will be added to one of the following stages of the job’s interview plan lead, application review, hired, archived if an existing application already exists, it will not be updated with the historic information (in the case of the candidate’s application being moved forward in ashby, rendering the imported information obsolete) • jobs jobs will be matched against the job titles of existing jobs before creating a new one if a new job is created, then they will follow the default interview plan on your ashby account as far as team and location go, they will be added to the job if a match is found when importing if no match is found, a generic location and team is used if jobs are not imported, then applications will be imported to a generic job we will not import the following • job postings • interview plans • openings gem ats what do we import? candidates candidates are matched to existing ashby profiles using email if no match is found, a new candidate is created any resumes included in the export are imported and linked to the correct candidate/application (gem assigns internal resume ids and we map those back to real filenames) applications gem ats exports application data across multiple csv files; we combine these into ashby job considerations existing applications are matched when possible; otherwise, new applications are created application history is reconstructed from gem’s application stages duplicate and conflicting entries (common in gem exports) are cleaned up if gem did not include a proper “hired” terminal stage, we infer and create a final hired stage archived applications are recreated with the correct archive reason, and the default ashby archive stages are removed/rebuilt for accuracy application feedback scorecards from gem are converted into notes if question/answer files are populated, we include mappings into the note where possible jobs job records can be imported if the customer includes them job titles are matched against existing ashby jobs before creating a new one location and team are added to the job if a match exists; otherwise, a generic option is used if jobs are not imported, applications are added to a generic job departments & offices gem exports include csvs for departments and offices we support matching or creating these entities, but department hierarchy is partially supported office hierarchy (like regions → offices) is not currently supported customers with complex hierarchies may require mapper updates we do not import the following from gem ats job postings interview plans openings complex hierarchical location/department structures post import once the import is complete, you’ll be notified by your success manager or the scaled success team if any information you’re expecting to see is missing, do let them know