✅ What stays the same in Guide?

Since Guide's chrome extension works exactly the same across all ATSs, your end-user workflows will remain unchanged:

What Guide will handle:

Create your new Ashby-linked Guide instance — we'll set up a new account connected to Ashby alongside your existing Greenhouse account
Enable the account switcher — you'll be able to toggle between your Greenhouse and Ashby Guide instances during the transition window, so no work is lost mid-flight
Migrate your existing content automatically:
- Email templates
- Candidate portal (Candidate.FYI) templates
- Message templates
Set up a shared Slack channel with a transition checklist canvas to track progress
Schedule training sessions — a product training call for your team + two 30-minute office hours sessions in the weeks following go-live

Confirm your target go-live date — we recommend a 1-week overlap period where both Greenhouse and Ashby instances are live
Audit and configure job settings in your new Ashby Guide instance — interview requirements work differently in Ashby vs. Greenhouse and must be set per job (Guide saves them after the first setup, so it's a one-time effort per role)
Connect the Ashby integration in your Guide settings
Reconnect Slack — this requires an admin/IT action (a quick ticket to your IT team)
Recreate user profiles in the new instance — most content migrates automatically, but user bios and scheduling preferences need to be set up manually
Review and link templates to your new Ashby jobs — templates transfer but won't be auto-linked to jobs initially
Configure your default calendars in org settings for the Ashby instance
Decide how to handle mid-flight candidates — we recommend moving all in-progress candidates to Ashby on launch day (Ashby syncs every 20 minutes to keep data flowing)
Training paths (if applicable): If you have existing interviewer training paths, these will need to be manually updated in Ashby to match your Greenhouse structure — we'll walk you through this

We recommend kicking off your Guide-to-Ashby migration ~2 weeks prior to your Ashby go-live date.

Date	Milestone
Nov 30	Ashby data and jobs fully configured
Dec 1	Connect Ashby to Guide & begin configuration
Dec 19	Ashby Go-Live — Guide fully migrated

Milestone	Owner
Guide creates Ashby instance + account switcher	Guide
Audit org/job settings in new Ashby instance	Customer
Configure Candidate portal content	Customer
Reconnect Slack integration	Customer (IT)
User profile setup for all team members	Customer
Product training session	Guide + Customer
Go-live (full cutover)	Both
Office hours (2 sessions, weeks 1–2 post-launch)	Guide

Dual Integration Setup
- Once you're ready to begin setting up your Guide instance for Ashby, reach out to your Guide CSM asking them to enable your Ashby sandbox.
- Once done, you will have access to both Greenhouse and Ashby environments in Guide.
- You'll see them listed as separate accounts in the Guide switcher (e.g., "Good Health - Greenhouse" and "Good Health - Ashby").
- Users can switch between them during the transition.
Connect Ashby to Guide
- Navigate to Settings > Integrations in Guide.
- Connect your Ashby account using your Ashby admin credentials.
Once connected, Guide will begin syncing Ashby jobs, candidates, and users.
Manually Input Email Templates
- Ashby does not expose email templates via API, so you’ll need to manually re-add any Guide templates.
- Go to Settings > Email Templates in your Ashby Guide environment.
- Copy over templates from your Greenhouse Guide environment.
Re-link Templates to Jobs (if needed)
- Once your Ashby jobs are synced, you may need to re-map your templates to the appropriate roles.
- This ensures job-specific tokens and links are working correctly.
User Onboarding
- When recruiters start using Guide in Ashby, they'll receive a one-time prompt to confirm their scheduling preferences (e.g., default meeting link, calendar settings).
- After setup, scheduling works exactly the same.

Once you're confident your team is fully live on Ashby:

Let us know you're ready to deprecate the Greenhouse instance.
We’ll disable the Greenhouse Guide environment so your team no longer sees it in the switcher.
No data will be lost; archived instances remain accessible to the Guide team for historical records.

Task	Owner	Timing
Connect Ashby to Guide	Recruiting Ops/Admin	~2 weeks before Ashby go-live
Manually copy email templates	Recruiting Ops	~2 weeks before Ashby go-live
Reconnect calendar/Zoom integrations	All users (if needed)	~2 weeks before go-live
Re-map templates to jobs	Recruiting Ops	Before go-live
Schedule migration support call with Guide	Recruiting Ops + Guide CSM	2 weeks before go-live