<aside> 💡

When migrating to Ashby from Comeet, you can now import historical data. Please note that the historical data can take two to three weeks to import and may not be ready for your go-live date.

</aside>

Import Overview

File-based migrations are a two-step process:

1. Importing active candidates and job considerations so they can be added to open jobs
2. Importing historical data for your records and reporting purposes

Active Jobs and Candidates

The import option documented here can be used for bringing in historical data. If you have open roles in Comeet 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 Creating & Posting Jobs. 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 Self**-serve importing candidates via bulk import**.

Kicking off the migration.

You can request a data export from Comeet here. Once you’ve received your exported data from your Comeet, your CSM or Onboarding team will send you a link via SendSafely so you can upload your exported files.

Importing Comeet Data into Ashby

Once we’ve received your files, our engineering team will get to work on the import. We import the following data:

• Candidates (including feedback listed as a note, notes, tags, resume, email, phone, social links and source)
• Applications (added to Ashby as job considerations)
• Jobs (optional)

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.

Applications