HRMS migration
Field-level mapping, validation, and rollback between Applicant Starter and Crelate. We move data and schema; workflows are rebuilt natively in Crelate.
Applicant Starter
Source
Crelate
Destination
Compatibility
9 of 12
objects map 1:1 between Applicant Starter and Crelate.
Complexity
BStandard
Timeline
2-4 weeks
Overview
Moving from Applicant Starter to Crelate is a capability upgrade, not a simple record copy. Applicant Starter's API has no public documentation, requires a paid plan for access, and paginates results without a bulk endpoint—all of which shape how we extract your data. Crelate receives the migrated records via its structured import layer, which we configure during scoping to match your Applicant Starter stage taxonomy and custom field schema. We preserve candidate name, email, phone, resume, stage history, and the full activity stream including emails, calls, and notes. Scorecard and evaluation data cannot export from Applicant Starter and requires manual handling; we document its location and format so your team can recreate it post-migration. We do not migrate workflows, job board distribution logs, or free-text automation rules—these are rebuilt by your admin using Crelate's workflow builder.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Applicant Starter object lands in Crelate, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Applicant Starter
Candidate
Crelate
Person (Candidate)
1:1Applicant Starter Candidate records map to Crelate Person records. We extract first_name, last_name, email, phone, and address fields and import them directly. The original Applicant Starter candidate ID is preserved in a custom reference field for audit and cross-referencing. Custom candidate fields require explicit mapping during scoping; we pull the field schema from Applicant Starter and match each to a Crelate field or flag it for new field creation.
Applicant Starter
Resume / Attachment
Crelate
Resume / File Attachment
1:1Resume files and binary attachments export as blobs from Applicant Starter, download with consistent naming (candidate name + original filename), and upload to Crelate as file attachments linked to the corresponding Person record. Large resume libraries require sequential download handling. We verify file integrity with MD5 checksum before upload.
Applicant Starter
Job Requisition
Crelate
Job
1:1Job postings, department, hiring manager, and open/closed status export cleanly from Applicant Starter. We map job_title, department, location, job_description, and status to Crelate Job fields. The original Applicant Starter job ID is preserved as a custom field for reference. Closed positions export on a best-effort basis depending on the plan tier; we flag any gaps during scoping.
Applicant Starter
Application / Pipeline Stage
Crelate
Pipeline Stage
lossyApplicant Starter's pipeline stages are user-defined, not fixed—accounts may use Applied/Screening/Interview or Open/Qualified/Closed or custom labels. We extract the full stage schema during scoping and build a custom stage map to Crelate pipeline stages. Stages with no direct Crelate equivalent are flagged for admin review. Activity timestamps are preserved in the activity stream attached to the Person record.
Applicant Starter
Activity: Email
Crelate
Activity (Email)
1:1Email engagement logs migrate to Crelate Activity records linked to the corresponding Person and Job. We preserve email subject, body, timestamp, and direction (sent/received). Activity ordering is preserved by setting the timestamp to the original Applicant Starter value. Older activity records may lack complete timestamps; we flag these and set a default date with a note.
Applicant Starter
Activity: Call
Crelate
Activity (Call)
1:1Call logs migrate to Crelate Activity records with call disposition and duration preserved. We map the call type and set the activity timestamp from the original log. Call recordings, if attached in Applicant Starter, export as file attachments and link to the Activity record.
Applicant Starter
Activity: Note
Crelate
Note
1:1Interview notes and general notes migrate to Crelate Note records attached to the corresponding Person, Job, or Client record. We preserve note body, author, and timestamp. Notes without timestamps receive a default date with a flag for admin review.
Applicant Starter
Job Distribution Log
Crelate
Job Distribution
1:1Tracks where a job was posted (LinkedIn, Indeed, etc.). This data exists in Applicant Starter but may be inconsistently recorded. We export available distribution records and map them to Crelate job distribution fields or custom fields. Gaps are flagged for manual verification.
Applicant Starter
Custom Field (Candidate)
Crelate
Custom Field (Person)
lossyCustom fields on candidates require explicit mapping during scoping. We pull the full custom field schema from Applicant Starter, match each to a Crelate field (creating new custom fields in Crelate where needed), and document the mapping in the field map deliverable. Fields with no Crelate equivalent are flagged for admin review.
Applicant Starter
Custom Field (Job)
Crelate
Custom Field (Job)
lossyCustom fields on job requisitions follow the same mapping process as candidate custom fields. We extract the job-level custom field schema, map to Crelate equivalents, and flag any unmapped fields for admin review.
Applicant Starter
Scorecard / Evaluation
Crelate
Not Migrated
1:1Scorecard data in Applicant Starter is stored in a proprietary format not accessible via the export API. We do not migrate scorecards. We notify customers during scoping, document the location and format of scorecard data in Applicant Starter, and advise manual export. Recreated scorecards can be built in Crelate using its custom form builder post-migration.
Applicant Starter
Tag / Taxonomy
Crelate
Tag
1:1Applicant Starter tag taxonomies are user-defined and vary per account. We extract the full tag schema during scoping and map tags to Crelate tags. Tags used for candidate classification map directly. Tags used for workflow or filtering purposes are documented separately for admin to recreate in Crelate's tagging system.
| Applicant Starter | Crelate | Compatibility | |
|---|---|---|---|
| Candidate | Person (Candidate)1:1 | Fully supported | |
| Resume / Attachment | Resume / File Attachment1:1 | Fully supported | |
| Job Requisition | Job1:1 | Fully supported | |
| Application / Pipeline Stage | Pipeline Stagelossy | Fully supported | |
| Activity: Email | Activity (Email)1:1 | Fully supported | |
| Activity: Call | Activity (Call)1:1 | Fully supported | |
| Activity: Note | Note1:1 | Fully supported | |
| Job Distribution Log | Job Distribution1:1 | Fully supported | |
| Custom Field (Candidate) | Custom Field (Person)lossy | Fully supported | |
| Custom Field (Job) | Custom Field (Job)lossy | Fully supported | |
| Scorecard / Evaluation | Not Migrated1:1 | Fully supported | |
| Tag / Taxonomy | Tag1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Applicant Starter gotchas
No public API documentation or developer portal
Export requires a paid plan
No native bulk export endpoint
Stage and tag schema varies per account
Crelate gotchas
120 req/min API rate limit throttles bulk migrations
20 custom field per-entity cap forces data model decisions
15,000-record export ceiling on single operations
Sequences and automation workflows do not migrate
API key is a querystring parameter, not a header
Pair-specific challenges
Migration approach
Scoping and API access verification
We audit the Applicant Starter account to verify paid-tier API access, enumerate the candidate count, job count, activity volume, and custom field schema. We extract the full pipeline stage taxonomy and tag taxonomy. We identify scorecard locations and any closed-position data. The scoping output is a written migration scope document covering record counts, field mappings, stage maps, and a list of any data that cannot migrate. If the account lacks paid-tier API access, we discuss alternatives before proceeding.
Stage schema extraction and Crelate pipeline configuration
We extract every distinct pipeline stage name and tag from Applicant Starter and build a custom stage map to Crelate pipeline stages. We configure the Crelate destination pipeline with matching stage values before any data loads. Custom fields on candidates and jobs are matched to Crelate fields or created as new custom fields. We document every mapping decision and flag any Applicant Starter fields with no Crelate equivalent for admin review.
Test migration and reconciliation
We run a test migration into Crelate using representative data volume. The customer reviews the output, spot-checks 25-50 records against the Applicant Starter source, and approves the field mapping and stage schema before production migration begins. Any mapping corrections happen here, not in production. We also verify resume file integrity and attachment linkage during this phase.
Candidate and job migration
We migrate candidates first because they are the primary record with dependencies (attachments, activities). We download resume files with consistent naming, then import Person records to Crelate with the resolved stage assignments and custom field values. Job requisitions follow, with original Applicant Starter job IDs preserved for reference. We resolve any Owner references by matching to existing Crelate users by email.
Activity history and attachment migration
We migrate the full activity stream—emails, calls, notes—after candidate records are loaded. Activities attach to the corresponding Person record with original timestamps preserved. Resume files upload as attachments linked to the Person record. We use MD5 checksum verification to confirm file integrity. Activity records without timestamps receive a default date and are flagged for admin awareness.
Cutover, validation, and rebuild handoff
We freeze Applicant Starter writes during the cutover window, run a final delta migration of any records modified during migration, and enable Crelate as the system of record. We deliver the written automation inventory covering any Applicant Starter workflow rules or free-text automation that requires rebuilding in Crelate's workflow builder. We do not rebuild these as part of the migration scope. We support a one-week hypercare window for reconciliation issues raised by the recruiting team.
Platform deep dives
Applicant Starter
Source
Strengths
Weaknesses
Crelate
Destination
Strengths
Weaknesses
Complexity grading
Standard HRMS migration. 1 of 7 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Applicant Starter and Crelate.
Object compatibility
1 of 7 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
7-object category — typical timelines run 2–7 days end-to-end.
API constraints
Applicant Starter: Not publicly documented.
Data volume sensitivity
Applicant Starter doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Applicant Starter to Crelate migration scoping. Not seeing yours? Book a call.
Walk through your Applicant Starter to Crelate migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Applicant Starter
Other ways to arrive at Crelate
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.