Migrate from Greenhouse to Ashby with precision & ease

A seamless, customizable migration solution for moving your Greenhouse data with perfect fidelity and minimal disruption.

Book free consultation
Greenhouse
Ashby
MIGRATION OVERVIEW

Why teams migrate from Greenhouse to Ashby

There is no native one-click migration path from Greenhouse to Ashby for custom API builds. Greenhouse uses a structured evaluation model with per-attribute scorecard ratings, while Ashby uses an analytics-first architecture with unified feedback forms.
The fundamental gap is scorecard fidelity — Greenhouse's attribute-level ratings have no direct equivalent in Ashby's feedback system, meaning years of structured interview data must be encoded as notes or accepted as lossy.
Every custom migration requires navigating expiring attachment URLs, Ashby's deceptive 200 OK error responses, and aggressive rate limits on both platforms.
KEY CHALLENGES

What makes this migration complex

These are the architectural mismatches and technical hurdles specific to a Greenhouse to Ashby migration.

Most Critical

Scorecard Fidelity Loss

Greenhouse's per-attribute scorecard ratings have no direct equivalent in Ashby's feedback model. Data must be encoded as structured HTML notes or accepted as lossy.

Attachment URL Expiration

Greenhouse hosts resumes on AWS S3 via signed temporary URLs that expire shortly after the API request. Scripts must download inline during extraction.

Ashby 200 OK Error Trap

Ashby returns HTTP 200 even for failed requests, with success indicated only in the response body. Scripts that check only status codes silently skip failed writes.

Rate Limit Choreography

Greenhouse allows 50 requests per 10 seconds while Ashby allows 1,000 per minute. Large migrations require hours of sustained API throughput with proper backoff.

Prospect Conversion

Greenhouse has an explicit Prospect type with its own pools. Ashby has no separate prospect concept, requiring a decision on how to represent these records.

COMPLETE COVERAGE

Intelligent Human-Verified Data Mapping

Our migration engineer precisely maps every data point from Greenhouse to Ashby, ensuring perfect continuity for your customer support operations.

Greenhouse
Ashby
Candidates
Candidate
Applications
Application
Jobs
Job
Job Posts
Job Posting
Job Openings
Opening
Offers
Offer
Scorecards
Feedback / Scorecard
Scheduled Interviews
Interview Schedule
Departments
Department
Offices
Location
Hiring Team
Hiring Team Member
Tags
Candidate Tag
Custom Fields
Custom Field
Attachments
File / Attachment
Activity Feed
Note
Rejection Reasons
Not Available

Looking for more entity mappings?

Contact our team
MIGRATION RISK ASSESSMENT

Every migration risk, already solved

Migration between platforms is full of edge cases. Our engineers have identified every risk from Greenhouse to Ashby and built proven solutions for each one.

Migration Challenge ClonePartner Status
High Complexity —
Solved
Scorecards
Per-attribute ratings cannot be replicated in Ashby's feedback model
Solved
Attachments (Resumes)
Signed S3 URLs expire — must download inline during extraction
Solved
Custom Engineering —
Handled
Prospect Records
No direct equivalent in Ashby; become candidates with lead status
Handled
Custom Fields
Type mismatches between platforms require pre-creation and normalization
Handled
Pipeline Stage History
Requires applicationHistory parameter to preserve stage movement timeline
Handled
Offers
Different approval workflow structures between platforms
Handled
Clean Transfer
Candidate Tags
Direct mapping via API with pre-creation required
Clean
Sources
Requires pre-creation in Ashby but maps cleanly
Clean
Notes
HTML-formatted notes transfer well via candidate.createNote
Clean
Rejection/Archive Reasons
Terminology differs but mapping is straightforward
Clean
2 high-complexity solved
4 custom-engineered
4 clean transfers
CUSTOM MIGRATION

Fully customizable engineer-led migration

Tailor your migration from Greenhouse to Ashby exactly to your needs with our flexible customization options. Our experts will configure the perfect migration plan for your business.

Migration Filters

Job Status Filter

Filter by open, closed, drafted, or archived positions

Candidate Stage

Select candidates based on pipeline stages or disposition

Hiring Team/Owner

Migrate records assigned to specific recruiters or managers

Time Range

Migrate candidates or jobs from a specific time period

Data Types

Candidates & Profiles

Resumes, contact details, and full candidate history

Jobs & Requisitions

Job openings, descriptions, and hiring team assignments

Interviews & Feedback

Interviewer scorecards, ratings, and internal notes

Offers & Applications

Application metadata, offer letters, and contract files

ZERO DOWNTIME

Your timeline. Our engineers.

A dedicated engineer runs your migration, planned around your schedule and your data.

No babysitting a wizard. Avoid debugging errors yourself.

Looking for a more detailed migration timeline?

Contact our team

Speed

The migration timeline depends on both our turnaround time and yours.

We can complete a migration in under a day when the accounts are connected and the sample migration is approved promptly.

Background Sync

We also support migrating the newest records first, so you can go live faster while the rest of the data is synced in the background.

Data Volume Impact

Larger data volumes may require longer migration windows.

Continuous Operation

Weekend migrations minimize disruption to your customer service operations.

MIGRATION TIMELINE

Your Greenhouse to Ashby migration, step by step

See how long your migration will take from start to finish. Drag the slider to estimate based on your data volume.

How many records are you migrating?

<10K 50K 100K 250K 500K 1M+
Checklist ~3 days
Sample 1 day
Review ~2 days
Full 2 days
Delta 1 day
Your team ClonePartner

Estimated total

~9 business days

1

Migration Checklist

1 day · ClonePartner ~2 days · Your team

We prepare the optimal data mapping as a shareable spreadsheet. Your team reviews, approves, and adds any customizations.

2

Sample Migration

1 day · ClonePartner

We run a test migration with a representative sample of your data to verify mapping accuracy and identify any potential issues before the full run.

3

Review & Approve

~2 days · Your team

Your team reviews the sample migration results, confirms data accuracy and mapping, and gives the go-ahead for the full migration.

4

Full Migration

2 days · ClonePartner

We execute the complete migration of all your data to your new Ashby, with real-time progress tracking and comprehensive logging.

5

Delta Migration

1 day · ClonePartner

We capture and transfer any new data that was added or updated during the main migration to ensure no data is lost. This final sync keeps everything current.

Timeline is an estimate. Actual duration depends on API rate limits, data complexity, and your team's availability.

Get an exact timeline

Complete Technical Guide

Greenhouse to Ashby Migration: APIs, Mapping & Rate Limits

Greenhouse to Ashby migration requires handling expiring attachment URLs, Ashby's 200 OK error trap, and lossy scorecard-to-feedback mapping. Budget 2–4 weeks minimum for custom builds.

26 min read

Read the guide

Pros and cons of different migration options

Choosing the right approach is key because migrating from Greenhouse to Ashby isn't just about moving data – it's about protecting customer relationships.

Feature / Criteria ClonePartner Automated Tools CSV Import In-house migration
Custom Scripting for complex data ✓ Engineers build & maintain ✗ No ⚠ Manual ✓ Yes – but costly
Sandbox & Pilot Migrations ✓ Full sandbox + pilot plans ⚠ Limited ✗ No ⚠ Often Informal
Manual validation & reconciliation ✓ Automated + manual QA ✗ No ✓ Yes (Manual) ✓ Heavy manual effort
Backup & rollback plan ✓ Robust procedures ✗ No ✗ No ⚠ Often incomplete
Handles automation and integrations ✓ Full support ⚠ Partial ✗ No ⚠ Possible but fragmented
Post-migration engineer support ✓ Dedicated engineers ✗ No ✗ No ⚠ Limited SLA
Adaptable to API changes ✓ Proactive adaptation ✗ No ⚠ Manual fixes ⚠ Slower response
Turnaround / SLA predictability ✓ Predictable SLAs ⚠ Fast but brittle ⚠ Slow and manual ⚠ Often slower
Data Security & Compliance ✓ High – enterprise grade ⚠ Medium (depends) ⚠ Low (manual) ⚠ Hidden gaps common
Pricing predictability ✓ Transparent & fixed ⚠ Low (per-job) ⚠ Low (manual hours) ⚠ High/variable OPEX
End-to-end project management ✓ Full E2E delivery & PM ✗ No ✗ No ⚠ Often partial
Business impact & opportunity cost ✓ No diversion of staff ✗ No ✗ No ⚠ Diverts engineering

What does an Engineer-led migration mean anyway?

Speed & Accuracy: Our Blended Method

We blend automation (smart scripts, bulk APIs) with human expertise for speed without risk. Our engineers manually check every mapping, validation, and exception.

You get:

  1. Speed of automation for bulk record migration
  2. Precision of engineers verifying integrity and business logic
  3. Pilot migrations and sandbox testing to catch issues early
  4. Real-time validation reports and rollback readiness
Result: 50x faster migrations than manual imports — with near-zero error rates.

Handling the Tricky Tech and API Details

The Greenhouse and Ashby APIs each behave differently, which is where our engineers shine. We build custom logic to handle the data quirks where generic tools typically break.

We handcraft API logic for:

  1. Field mapping and transformation
  2. Pagination, rate-limit handling, and throttling
  3. Preserving conversation threads, attachments, and internal notes
  4. Syncing custom fields, SLAs, and macros without breaking structure
Our scripts: Natively retry failed calls, re-queue large attachments, and ensure data parity.

No Guesswork

We don't just promise smooth migrations—we measure and prove them. Every client receives a Migration Validation Report with all metrics.

Typical results across projects:

  1. 100% record-count parity between your Greenhouse data and Ashby
  2. Zero downtime during staged cutovers
  3. 99.9% attachment integrity (verified via checksum)
  4. Full automation and preservation of all business rules
Our standard: Includes full SLA preservation and 48 hours of engineer-assigned support post go-live.

We Adapt to Your Setup (Not the Other Way Around)

No two teams configure Greenhouse or Ashby exactly the same way—with unique automations and data. We customize every migration script to fit your exact workflow, tags, and triggers.

Our engineers adapt for:

  1. Custom fields, ticket forms, and workflows
  2. Multi-brand or multi-language setups
  3. Historical imports and partial (date-based) migrations
  4. Integration re-mapping for CRMs, chat, or feedback tools
The promise: If your data doesn't fit a standard template, we build one just for you.

Enterprise-Grade Security & Compliance

Your customer data is precious. Our migration process maintains the highest standards of security and regulatory compliance.

SOC 2 Type II

Independently audited compliance with rigorous security standards

ISO 27001

Certified information security management system

GDPR

Full compliance with EU data protection regulations

HIPAA

Certified for handling protected health information

AES-256 Encryption

Bank-grade encryption for all stored credentials

Latest TLS

Secure transfer protocol for all data in transit

Role-Based Access

We follow role-based access control for every migration project

Scheduled Deletion

Automatic data purging after migration completion

FAQ

Frequently Asked Questions

Everything you need to know about migrating from Greenhouse to Ashby. Can't find what you're looking for? Talk to our team.

How long does a Greenhouse to Ashby migration take?
Ashby's CSM-led native API migration typically completes in 2–3 days depending on data volume. Custom API-based migrations require 2–4 weeks of engineering effort plus validation time. Smaller teams using CSV can finish in days but lose scorecard and attachment data.
Does Ashby preserve Greenhouse scorecards during migration?
Ashby's native migration explicitly includes scorecards. However, Ashby's feedback model does not replicate Greenhouse's per-attribute scorecard ratings. For custom API migrations, scorecards can be preserved by encoding them as structured HTML notes on candidate profiles, or by mapping overall recommendations to Ashby feedback forms.
What are the Greenhouse and Ashby API rate limits?
Greenhouse Harvest enforces approximately 50 requests per 10 seconds (v1/v2) or per 30-second window (v3). Ashby enforces 1,000 requests per minute per API key, with a separate Report API limit of 15 requests per minute. For large migrations (50K+ candidates), the load phase alone can take several hours.
Why do Greenhouse attachment URLs break during migration?
Greenhouse hosts resumes and attachments on AWS S3 via signed, temporary URLs. These URLs expire shortly after the API request. Any migration script must download attachments immediately during extraction — never as a deferred batch job.
What is the Ashby 200 OK error trap?
Ashby's API returns HTTP 200 status codes even for failed requests, with a 'success: false' flag in the JSON response body. Migration scripts that only check HTTP status codes will silently skip failed writes. Always parse the response body and check the success field.
How long does the Greenhouse to Ashby migration take?
Most migrations complete within 1–5 business days, depending on data volume and complexity. We provide a detailed timeline after the initial assessment and can often complete small migrations in under 24 hours.
Will my team lose access to Greenhouse during the migration?
No. Your source system remains fully operational throughout the entire migration. We run the migration in the background with zero downtime to your current operations.
Will there be downtime when migrating from Greenhouse to Ashby?
No. Our migration process is designed for zero downtime. We use a staged approach with background sync and a fast cutover, ensuring no disruption to your live business operations.
How do I validate that everything migrated correctly?
Every client receives a Migration Validation Report with comprehensive metrics including record-count parity, attachment integrity verification via checksum, and full audit logs. We also offer unlimited sample migrations so you can verify before committing.
Do I need professional help for this migration?
While simple migrations can sometimes be handled in-house, professional help ensures zero data loss, proper field mapping, and preservation of relationships between records. Our engineer-led approach catches edge cases that automated tools miss.
Does ClonePartner provide guidance before committing?
Yes. We provide a free consultation and assessment. We'll review your data structure, discuss your requirements, and provide a detailed migration plan and fixed-price quote before you commit to anything.

Still have questions?

Book a free 30-minute consultation with our migration engineers. We'll walk you through the exact approach for your Greenhouse→Ashby migration.

Contact our team

Ready to start your
Ashby Migration?

Join hundreds of businesses who have successfully migrated with ClonePartner. Let's discuss your migration needs and build a plan that works for you.

Book free consultation

Attention to Detail

We meticulously handle every aspect of your migration, ensuring no data is lost during transfer and mapping every field correctly between platforms.

Custom Solutions

Every business is unique. We tailor your migration strategy to match your specific requirements, workflows, and data structures.

Security & Compliance

Your customer data is handled with enterprise-grade security protocols, ensuring compliance with GDPR, HIPAA, and industry standards.