Migrate from Workable to Greenhouse

KEY CHALLENGES

What makes this migration complex

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

Most Critical

Candidate-to-Application Model Translation

Workable stores candidates as flat per-job records, requiring deduplication by email and remapping into Greenhouse's separate Candidate and Application objects to preserve multi-job candidacy relationships.

Blocks all downstream imports if mapped wrong

Bulk Resume Extraction Bottleneck

Workable's CSV export excludes resume files entirely, forcing teams to use individual API calls per candidate or request a full account data export that requires archiving all active jobs.

API Rate Limit Constraints

Workable's account-token rate limit of 10 requests per 10 seconds and Greenhouse's own API throttling make large-scale migrations (10,000+ candidates) take hours of continuous API calls with careful backoff logic.

Scorecard and Activity History Loss

Workable evaluations and interview feedback do not map directly to Greenhouse's scorecard-per-application-per-interview structure, and CSV bulk import drops this data entirely.

Pipeline Stage Mapping Complexity

Workable stages are properties of the candidate record, while Greenhouse stages belong to the Application object within a job's interview plan, requiring careful per-job stage alignment and historical candidate workarounds.

Greenhouse API Version Deprecation

Greenhouse Harvest API v1 and v2 will be deprecated after August 31, 2026, meaning any new migration integration must target v3 with OAuth 2.0 authentication instead of Basic Auth.

MIGRATION RISK ASSESSMENT

Every migration risk, already solved

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

High complexity

Resumes and Attachments

Workable does not support bulk resume downloads natively, and Greenhouse's bulk import can silently drop resumes if email parsing fails to match the file to a candidate row.

Solved
Scorecards and Evaluations

Workable evaluations do not map to Greenhouse's scorecard-per-application-per-interview model, and CSV-based migration methods lose this data entirely.

Solved
Interview Feedback and Activity History

Detailed activity timelines, comments, and interview feedback are lost in CSV exports, and interviews cannot be backdated in Greenhouse even though scorecards can.

Solved

Custom engineering

Candidate Records

Candidates must be deduplicated by email across multiple Workable job records and consolidated into single Greenhouse Candidate objects, with risk of missed duplicates or unintended merges from Greenhouse's auto-merge feature.

Handled
Applications

Each Workable per-job candidate record must be re-created as a separate Greenhouse Application linked to the correct Candidate and Job, requiring careful relational mapping that has no direct CSV equivalent.

Handled
Pipeline Stages

Stages belong to different objects in each system (candidate in Workable vs. application in Greenhouse), and historical candidates cannot be placed into accurate pipeline stages without container-job workarounds.

Handled
Custom Fields

Greenhouse bulk import only supports simple custom field types (short text, number, single select, URL, Yes/No), so complex custom fields require API-based migration.

Handled
GDPR/CCPA Compliance Data

Candidate consent records and data retention policies may not transfer cleanly between platforms, requiring manual verification to maintain compliance during the migration.

Handled

Clean transfer

Jobs and Job Structures

Job records are relatively straightforward to recreate in Greenhouse, though interview plans, approval workflows, and scorecard templates must be manually configured.

Clean
Sources and Tags

Candidate sources and tags export cleanly from Workable's CSV and API and can be mapped to Greenhouse's source and tag fields with minimal transformation.

Clean

What Our Customers Say

Real migration stories

Direct Review

“They were SO helpful. We had a few hiccups because our migration was in the middle of the process, but they were really flexible and did multiple delta migrations for us. We were able to map a lot of our old ticket data so it's usable for comparisons in the future.”

Direct Review

“Overall a great experience. We had to go back a few times to get everything just right, which was totally expected. The transition was smooth, and there was no data loss.”

Direct Review

“One of the easiest migrations I've ever been through. The team took care of everything — all our data, customer interactions and macros. The process was clear, straightforward and we felt supported all the way. An absolutely seamless experience for our support team and our customers.”

Direct Review

“Fantastic at both guiding us through the process and helping us fix things as they come up and dial them in.”

Reviewed on G2

“The ease of the process and that ClonePartner was informing me what was going on at every step. If you're on the fence, do it. ClonePartner are great!”

See all customer stories →

CUSTOM MIGRATION

Fully customizable engineer-led migration

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

Migration Filters

Data Types

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 Workable to Greenhouse 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 2M 5M 10M+

Checklist ~3 days

Sample 1 day

Review ~2 days

Full 2 days

Delta 1 day

Your team ClonePartner

Estimated total

~9 business days

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.

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.

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.

Full Migration

2 days · ClonePartner

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

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.

Pros and cons of different migration options

Choosing the right approach is key because migrating from Workable to Greenhouse isn't just about moving data – it's about protecting your candidate experience and hiring pipeline.

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 hiring support
Adaptable to API changes	✓ Proactive adaptation	✗ No	⚠ Manual fixes	⚠ Slower response
Turnaround / hiring predictability	✓ Predictable hiring timelines	⚠ 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:

Speed of automation for bulk record migration
Precision of engineers verifying integrity and business logic
Pilot migrations and sandbox testing to catch issues early
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 Workable and Greenhouse 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:

Field mapping and transformation
Pagination, rate-limit handling, and throttling
Preserving candidate history, resumes, and scorecards
Syncing custom fields, pipelines, and scorecards 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:

100% record-count parity between your Workable data and Greenhouse
Zero downtime during staged cutovers
99.9% attachment integrity (verified via checksum)
Full automation and preservation of all business rules

Our standard: Includes full pipeline and scorecard 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 Workable or Greenhouse exactly the same way—with unique hiring workflows and data. We customize every migration script to fit your exact workflow, pipelines, and scorecards.

Our engineers adapt for:

Custom fields, hiring workflows, and scorecards
Multi-brand or multi-role setups
Historical imports and partial (date-based) migrations
Integration re-mapping for HRIS, background-check, or assessment 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 Workable to Greenhouse. Can't find what you're looking for? Talk to our team.

Can I export resumes from Workable in bulk?

No. Workable's Candidate Details CSV excludes resumes and files. You can either request a full account data export from Workable support (which requires archiving all jobs and is all-or-nothing) or use the Workable API to download resumes individually from URLs in candidate detail responses. ([help.workable.com](https://help.workable.com/hc/en-us/articles/115014887828-How-do-I-export-candidate-data))

What are the Workable API rate limits for data extraction?

Workable limits account tokens to 10 requests per 10 seconds and OAuth/Partner tokens to 50 requests per 10 seconds. Exceeding these returns HTTP 429. Monitor the X-Rate-Limit-Remaining header and pause before hitting zero. ([help.workable.com](https://help.workable.com/hc/en-us/articles/4903195036183-Troubleshooting-API-issues))

How does Greenhouse's data model differ from Workable's?

Workable associates candidates directly with jobs as flat records. Greenhouse separates Candidates (the person) from Applications (the candidacy for a specific job). One Candidate can have multiple Applications. You must deduplicate Workable records by email and create one Candidate per person with separate Applications per job. ([support.greenhouse.io](https://support.greenhouse.io/hc/en-us/articles/360001905032-Business-Intelligence-Connector-data-model))

Is Greenhouse Harvest API v1 being deprecated?

Yes. Harvest API v1 and v2 will be deprecated and unavailable after August 31, 2026. All new integrations should use Harvest v3, which requires OAuth 2.0 authentication instead of Basic Auth and uses a 30-second fixed-window rate limit.

How many candidates can I bulk import into Greenhouse at once?

Greenhouse recommends a maximum of 8,000 candidates per bulk import batch. The resume .zip file has a 5 GB size limit. The bulk import tool is only available on Plus and Pro subscription tiers. For larger datasets, split into multiple imports or use the Harvest API. ([support.greenhouse.io](https://support.greenhouse.io/hc/en-us/articles/38329467264027-Adding-historical-candidates-to-Greenhouse-using-bulk-import))

How long does the Workable to Greenhouse 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 Workable 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 Workable to Greenhouse?

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 Workable→Greenhouse migration.

Contact our team

Ready to start your
Greenhouse 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.

Migrate from Workable to Greenhouse with precision & ease

Why teams migrate from Workable to Greenhouse

What makes this migration complex