Greenhouse → Ashby Recruiting API Migration Guide

follow this guide to initiate the data migration from greenhouse to ashby recruiting generate an api key and web hooks the greenhouse integration requires you set up an api key and 15 web hooks for the api key, you’ll generate it in greenhouse and add it to ashby for the web hooks, see below for details on how to access these within your ashby account api key generate the api key navigate to https //t sidekickopen87 com/s3t/c/5/f18dqhb0s7kf8cvq7cv737b159hl3kw7 k2841cx6ngw35qnwb7vbmm2vs7 5r4jjn7hf197v5y04?te=w3r5hfj4cm2zww3zfpsj3p5vtyw41szxf4chywxw43nmxy41rl2hw4hlxw73h4thhw3f6jtz3k8k67w49kv7g41yyh 3b7b2\&si=8000000017570661\&pi=5070c0ee fe05 4d70 e62c 9cbe782f56bb in greenhouse create a harvest type api key, check both harvest v1 and harvest v3 and grant permissions for all "get" endpoints add the api key to ashby go to https //app ashbyhq com/ and sign in with google you should be able to sign in with your g suite account add the api key to your https //t sidekickopen87 com/s3t/c/5/f18dqhb0s7kf8cvq7cv737b159hl3kw7 k2841cx6ngw35qnwb7vbmm2vs7 5r4jjn7hf197v5y04?te=w3r5hfj4cm2zww3zfpsj3zh1bdw4rybcs3fbt5sw3z8pwd41prypw4fgbqv3zhs7sw41y26w49kvdzn3r3clz1v3\&si=8000000017570661\&pi=5070c0ee fe05 4d70 e62c 9cbe782f56bb webhooks your secret key and endpoint url both your endpoint url and secret key can be found on the https //t sidekickopen87 com/s3t/c/5/f18dqhb0s7kf8cvq7cv737b159hl3kw7 k2841cx6ngw35qnwb7vbmm2vs7 5r4jjn7hf197v5y04?te=w3r5hfj4cm2zww3zfpsj3zh1bdw4rybcs3fbt5sw3z8pwd41prypw4fgbqv3zhs7sw41y26w49kvdzn3r3clz1v3\&si=8000000017570661\&pi=5070c0ee fe05 4d70 e62c 9cbe782f56bb page within the webhook configuration section configure webhooks this will be the longest step, as it will be configuring 15 webhooks this step is required to ensure key events are accurate synced between ashby and greenhouse 1\ open the configuration section and go to dev center and select webhooks 2 select the first webhooks option 3 create a new webhook for all the events that should be sent to ashby you should now create a new webhook for each event below be sure to add your endpoint url and secret key to the endpoint url and secret key fields both your endpoint url and secret key can be found on the https //t sidekickopen87 com/s3t/c/5/f18dqhb0s7kf8cvq7cv737b159hl3kw7 k2841cx6ngw35qnwb7vbmm2vs7 5r4jjn7hf197v5y04?te=w3r5hfj4cm2zww3zfpsj3zh1bdw4rybcs3fbt5sw3z8pwd41prypw4fgbqv3zhs7sw41y26w49kvdzn3r3clz1v3\&si=8000000017570661\&pi=5070c0ee fe05 4d70 e62c 9cbe782f56bb page within the webhook configuration section create a new webhook for the following events delete candidate merged candidate candidate has changed stage candidate hired candidate unhired candidate anonymized candidate or prospect has been rejected candidate or prospect has been unrejected delete application interview deleted offer deleted scorecard deleted department deleted office deleted job deleted let your customer success manager or startup customer success team know when this is done and we'll import your data! what information is migrated from greenhouse? the following data is pulled over from greenhouse via an api migration departments offices jobs openings job stages custom fields candidates (including candidate notes) users (🚨 user permissions, however, are explicitly not mapped) scorecards sources candidate tags job posts offers (existing offers, offer data and offer letters are migrated and can be found within candidate profiles but offer letter templates are not pulled over) resumes rejection reasons we sync rejection reasons and rejection reason custom fields rejection reason fields in greenhouse are synced over as custom fields for archive reasons in ashby rejection questions scheduled interviews degrees disciplines eeoc email templates both organization and personal email templates are migrated over to ashby we do not replace placeholder tokens, so templates must be updated to include {{substitution tokens}} in ashby close reasons demographic questions (this comes over as a diversity survey in ashby) application form submissions emails can also be synced and mapped upon request faq 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 d o you migrate prospects from greenhouse? we don’t map any prospect related data into ashby so candidates with only a prospect application get mapped into ashby as candidates with a lead status they will not have a job consideration attached to their profile w hy can’t i see the email templates migrated from greenhouse in my account? as the substitution tokens in your email templates will need to be replaced with ashby tokens, email templates are synced over as archived templates we would recommend updating your email templates and then restoring them to use them moving forward to amend and restore your email templates, head to admin > organization setup > email templates then use the active dropdown to switch the view to see all email templates click on the email template in question and make the updates required, clicking on the t icon in the email toolbar to access and add in substitution tokens (more on these at ) once you’ve updated your email template click more and restore on the email template to make it an active template