Migrate from Pinpoint to Greenhouse

MIGRATION OVERVIEW

Why teams migrate from Pinpoint to Greenhouse

The core problem

Migrating from Pinpoint to Greenhouse has no native automated path and requires a purpose-built API-to-API pipeline for any dataset where data fidelity or compliance retention matters. Both systems use an application-centric model — candidates link to applications, applications link to jobs — but diverge sharply at the evaluation layer: Greenhouse enforces rigid, attribute-rated scorecards and mandatory stage-specific interview kits, while Pinpoint uses a more flexible, automation-driven evaluation framework. Pinpoint's API follows the JSON:API specification (requiring envelope deserialization and relationship resolution), whereas Greenhouse's Harvest v3 API uses standard REST JSON with OAuth 2.0 and cursor-based pagination. Custom transformation logic is required to map Pinpoint's custom attributes, pipeline stages, and talent pool constructs to Greenhouse's structured equivalents, and all organizational infrastructure (users, offices, departments, jobs, stages) must be pre-built in Greenhouse before any candidate or application data can be loaded.

Why this matters for your migration

KEY CHALLENGES

What makes this migration complex

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

Most Critical

JSON:API Envelope Deserialization

Pinpoint's API wraps all responses in a JSON:API envelope with nested 'data', 'attributes', and 'relationships' objects that must be unwrapped and relationship IDs resolved before data can be mapped to Greenhouse's flat REST JSON format.

Blocks all downstream imports if mapped wrong

Greenhouse Infrastructure Pre-Build Requirement

Greenhouse enforces a strict load order — users, offices, departments, jobs, and stages must all exist before any application or candidate POST requests are made, or requests will fail with reference errors.

Scorecard Structure Incompatibility

Pinpoint's flexible, per-stage scorecard model does not map cleanly to Greenhouse's mandatory, attribute-rated, interview-kit-bound scorecard structure, resulting in partial evaluation data loss on any migration path.

Attachment Extraction and Expiry Risk

Pinpoint document attachments are only accessible via API (not CSV export), and once written to Greenhouse, attachment URLs are signed S3 links that expire after 7 days, requiring careful sequencing and verification of document transfer.

Multi-Application Candidate Deduplication

A candidate who applied to multiple jobs in Pinpoint must be created as a single Greenhouse Candidate object with multiple child Application objects, requiring deduplication logic to prevent the creation of duplicate candidate records.

Pinpoint Pagination Drift Risk

Pinpoint uses page-number pagination (not cursor-based) with a maximum page size of 1,000 records, meaning records inserted during extraction can cause duplicates or gaps that must be mitigated by anchoring filters to the extraction start timestamp.

MIGRATION RISK ASSESSMENT

Every migration risk, already solved

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

High complexity

Pipeline Stage History

Stage-movement timestamps are silently dropped by CSV export methods and only partially recoverable via API, meaning historical progression data is at significant risk of loss on all but a full API-to-API migration.

Solved
Scorecards and Evaluation Notes

Pinpoint's flexible scorecard model cannot be fully reconciled with Greenhouse's rigid, attribute-rated, interview-kit-bound structure, resulting in an estimated 5–15% data loss even on a full API migration path.

Solved
Document Attachments

Attachments are entirely inaccessible via CSV export and must be extracted and re-posted via API, with Greenhouse's signed S3 URLs expiring after 7 days introducing a narrow verification window.

Solved
Talent Pools and CRM Data

Pinpoint's CRM-style talent pipelines have no direct Greenhouse equivalent — Greenhouse uses separate Prospect pools — meaning talent pool membership, engagement history, and nurture data cannot be migrated without significant custom handling or accepted loss.

Solved

Custom engineering

Applications

Application objects translate relationally between systems, but source attribution, referral data, and rejection reason mappings require manual configuration and some values may have no direct Greenhouse equivalent.

Handled
Custom Fields

Pinpoint supports Custom Attributes and Custom Fields while Greenhouse keys custom fields to specific objects (candidate, application, job, offer), requiring explicit field-level mapping decisions that may leave some Pinpoint attributes with no target.

Handled
Compliance and Audit Records

EEOC/OFCCP data and offer-approval audit trails require careful field-level mapping and may require the full API migration path to preserve the timestamps and attribution needed to satisfy compliance retention requirements.

Handled

Clean transfer

Candidate Records

Both systems maintain a discrete candidate profile object with standard fields (name, email, phone, social links), making direct mapping straightforward as long as deduplication logic is applied for multi-application candidates.

Clean
Jobs and Organizational Structure

Jobs, offices, and departments can be pre-built in Greenhouse before migration begins and represent a known, finite dataset, though stage plan configurations must be manually replicated per job.

Clean
Users and Permissions

Recruiter, hiring manager, and coordinator user records must be created in Greenhouse before candidate data is loaded, but the user dataset is typically small and stable with predictable mapping.

Clean

What Our Customers Say

Real migration stories

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!”

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.”

See all customer stories →

CUSTOM MIGRATION

Fully customizable engineer-led migration

Tailor your migration from Pinpoint 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 Pinpoint 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 Pinpoint 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 Pinpoint 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 Pinpoint 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 Pinpoint 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 Pinpoint to Greenhouse. Can't find what you're looking for? Talk to our team.

Can I migrate from Pinpoint to Greenhouse using a CSV export?

Only for very small datasets under 500 candidates where you don't need historical hiring data. CSV exports flatten relational structures, drop stage-movement timestamps, and cannot include document attachments. Pinpoint's help docs confirm that resumes and documents export separately and must be manually re-attached. For any production migration, use the API-to-API approach or Greenhouse's historical bulk import.

Does Greenhouse support backdating stage movements during migration?

No. Greenhouse does not support backdating stage movements via the API. You can place candidates in their final stage, but you cannot recreate the step-by-step progression with historical timestamps. Serialize the full stage history as a structured note on the candidate's activity feed.

Which Greenhouse API should I use for a Pinpoint migration?

Use the Harvest v3 API (OAuth 2.0). It provides full read/write access to candidates, applications, notes, and attachments. The Candidate Ingestion API is simpler but lacks scorecard writes, attachment uploads, and deep custom field support. Harvest v1/v2 will be unavailable after August 31, 2026.

How long does a Pinpoint to Greenhouse migration take?

For under 1,000 candidates, expect 2–3 weeks of engineering time. For 1,000–10,000, plan 4–6 weeks. Over 10,000 candidates typically takes 6–10 weeks due to rate limits, attachment handling, deduplication, and validation. Calendar time often exceeds engineering time due to cutover coordination.

How do I avoid missing confidential jobs during Pinpoint extraction?

Pinpoint excludes confidential jobs from API responses unless you explicitly include 'confidential' in the job visibility filter. Run extracts with an admin-grade account because Pinpoint report exports are also visibility-dependent — a restricted user will produce a partial dataset.

How long does the Pinpoint 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 Pinpoint 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 Pinpoint 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 Pinpoint→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 Pinpoint to Greenhouse with precision & ease

Why teams migrate from Pinpoint to Greenhouse