JobScore to Pinpoint Migration

MIGRATION OVERVIEW

Why teams migrate from JobScore to Pinpoint

The core problem

Migrating from JobScore to Pinpoint is a data-model translation problem with no native migration path between the two platforms, requiring fully custom extraction, transformation, and loading scripts. JobScore exposes candidate and application data via a flat REST JSON API gated behind an Enterprise plan, while Pinpoint follows the JSON:API specification with compound documents and relationship sideloading, meaning every response envelope and field mapping must be explicitly handled in code. The structural mismatch is significant: JobScore stores notes, feedback, and stage history at the candidate or application level in a flat schema, whereas Pinpoint isolates all activity strictly to the Application object, requiring careful entity-level routing during transformation. Custom work is required for source attribution mapping across 12 JobScore source types to Pinpoint's constrained channel enum, job record pre-creation in the Pinpoint UI due to the absence of a public POST /jobs endpoint, document binary re-attachment, and EEO data handling.

Why this matters for your migration

KEY CHALLENGES

What makes this migration complex

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

Most Critical

No Public Job Creation Endpoint

Pinpoint's public API only supports job updates, not creation, so all historical job records must be manually created in the Pinpoint UI and their resulting IDs captured before any application import can begin.

Blocks all downstream imports if mapped wrong

JSON:API Structural Transformation

JobScore returns flat JSON objects while Pinpoint requires JSON:API-compliant payloads with typed data envelopes, relationship objects, and sideloaded includes, necessitating a full structural transformation layer in migration scripts.

Source Attribution Schema Mismatch

JobScore stores a single candidate-level source across 12 typed source categories with sub-fields, while Pinpoint applies source attribution per application via a restricted channel enum plus a 255-character channel_source free-text field, requiring explicit mapping logic and detail preservation.

Activity Entity Ownership Conflict

JobScore associates notes, interview feedback, and stage history at either the candidate or application level, whereas Pinpoint binds all such activity exclusively to the Application object, requiring precise routing to avoid creating overlapping or misattributed history.

API Access and Rate Limit Constraints

JobScore API access is gated behind the Enterprise plan and capped at 3,600 GET requests per hour, while Pinpoint enforces IP-based rate limits of approximately 120 requests per minute, requiring coordinated throttling and adaptive backoff on both sides of the pipeline.

Document Binary Re-Attachment

Resumes, cover letters, and note attachments must be individually downloaded from JobScore's binary document endpoint and re-uploaded to Pinpoint, as CSV exports omit document binaries entirely and both APIs treat file transfer as a separate operation from metadata migration.

MIGRATION RISK ASSESSMENT

Every migration risk, already solved

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

High complexity

Applications

Applications depend on pre-existing Pinpoint Job IDs that must be manually created in the UI before import, and any mismatch in job ID mapping will orphan application records or attach them to incorrect job postings.

Solved
Jobs

No public POST /jobs endpoint exists in Pinpoint's API, meaning all job records require manual UI creation prior to migration, making this the highest-effort sequential dependency in the entire migration pipeline.

Solved
Notes and Interview Feedback

JobScore stores notes and interview feedback with named ratings and numeric scores (1.0–4.0) at the candidate or application level, and these must be explicitly routed to the correct Pinpoint Application object or they will appear against the wrong hiring timeline.

Solved
EEO Data

EEO fields including gender, race, veteran status, and disability status are served by a dedicated JobScore endpoint not included in standard exports, and mishandling this compliance-sensitive data during transformation or loading carries legal and regulatory risk.

Solved
Stage History

JobScore's workflow stage history and disposition codes are not preserved in CSV exports and require API extraction, and because Pinpoint's stage model is job-specific and customizable, each stage must be mapped individually before import or stage-movement history will be lost.

Solved

Custom engineering

Candidates

Pinpoint deduplicates candidates by primary email address, but the exact behavior when a duplicate email is POSTed — conflict error versus silent linking — varies by account configuration and must be verified before relying on it for automated deduplication.

Handled
Documents

Binary files must be downloaded individually from JobScore's document download endpoint and re-uploaded to Pinpoint as separate API operations, introducing transfer failure risk and requiring retry logic and post-migration attachment verification.

Handled
Source Attribution

JobScore's 12 source types with typed sub-fields must be mapped to Pinpoint's restricted channel enum plus a 255-character channel_source field, and lossy mappings such as network to referral or other to undetermined will degrade source reporting fidelity in the target system.

Handled
Offers

JobScore offer records include status, extended and accepted dates, start date, and custom offer field values that have no guaranteed structural equivalent in Pinpoint, requiring field-level mapping decisions that may result in data stored in custom attributes rather than native offer fields.

Handled

Clean transfer

Tags

Pinpoint distinguishes between candidate-level and application-level tags, so JobScore candidate tags must be deliberately assigned to the correct Pinpoint entity during migration, but the underlying data is straightforward string values with low transformation complexity.

Clean

What Our Customers Say

Real migration stories

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

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

See all customer stories →

CUSTOM MIGRATION

Fully customizable engineer-led migration

Tailor your migration from JobScore to Pinpoint 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 JobScore to Pinpoint 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 Pinpoint, 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 JobScore to Pinpoint 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 JobScore and Pinpoint 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 JobScore data and Pinpoint
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 30 days of engineer-assigned support post go-live.

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

No two teams configure JobScore or Pinpoint 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 JobScore to Pinpoint. Can't find what you're looking for? Talk to our team.

Does JobScore have an API for data migration?

Yes. JobScore offers a Hire API v2 at api.jobscore.com/v2, but it is restricted to Enterprise customers and select partners. The API supports extracting candidates, applications, jobs, documents, notes, EEO data, and offers. Non-Enterprise plans are limited to CSV exports which lose relational data and attachments.

Can I migrate from JobScore to Pinpoint with CSV only?

Only for small, low-fidelity moves. JobScore's Excel export covers basic fields like name, email, status, and source. Pinpoint's self-service import is job-by-job CSV with documents typically re-added manually. You lose interview feedback, notes, attachments, stage history, and EEO data.

What are the rate limits for JobScore and Pinpoint APIs?

JobScore allows 3,600 GET requests/hour and 400 write requests/hour with a 20 request/minute burst cap. Pinpoint allows roughly 120 requests per IP per minute and 240 per 8 minutes. For a 10,000-candidate migration with documents, expect 2–3 days of continuous processing.

Will Pinpoint email candidates when I import historical data?

Yes, by default. Pinpoint's application create endpoint triggers both applicant and internal notifications. Migration loads must use skip_notifications_on_create: true to prevent thousands of spurious emails.

How do I handle interview feedback from JobScore in Pinpoint?

JobScore stores interview feedback as notes with named ratings on a 1.0–4.0 scale. Pinpoint uses a different evaluation model with structured scorecards. The most practical approach is to flatten rating names and scores into the note's HTML content during migration, preserving the data without loss.

How long does the JobScore to Pinpoint 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 JobScore 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 JobScore to Pinpoint?

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 JobScore→Pinpoint migration.

Contact our team

Ready to start your
Pinpoint 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 JobScore to Pinpoint with precision & ease

Why teams migrate from JobScore to Pinpoint