HRMS migration

Migrate from Applicant Starter to Crelate

Field-level mapping, validation, and rollback between Applicant Starter and Crelate. We move data and schema; workflows are rebuilt natively in Crelate.

Applicant Starter logo

Applicant Starter

Source

Crelate

Destination

Crelate logo

Compatibility

75%

9 of 12

objects map 1:1 between Applicant Starter and Crelate.

Complexity

BStandard

Timeline

2-4 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Applicant Starter logo

Applicant Starter

What's pushing teams away

  • Teams outgrow the platform when hiring volume increases beyond what the UI can manage efficiently, citing lack of advanced analytics and reporting.
  • Customers report limited customization options for pipeline stages and candidate evaluation workflows, pushing them toward platforms like Workday or Greenhouse.
  • Integration options beyond job boards are sparse, and teams needing HRIS sync or advanced CRM features find the ecosystem insufficient.

Choosing

Crelate logo

Crelate

What's pulling them in

  • Affordable per-seat pricing with transparent tiers makes Crelate accessible for small-to-mid staffing firms evaluating ATS platforms for the first time.
  • Fast implementation reported by customers—some describe getting live in a matter of minutes with support team assistance.
  • Unified ATS + CRM in a single product eliminates the need to buy and synchronize separate recruiting and sales tools.
  • Flexible custom fields across Contacts, Companies, and Opportunities allow recruiting teams to capture firm-specific data without developer involvement.
  • Positive reviews highlight the product's intuitive interface and functional breadth for teams that need recruiting workflows without enterprise overhead.

Object mapping

How Applicant Starter objects map to Crelate

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

maps to

Crelate

Person (Candidate)

1:1
Fully supported

Applicant 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

maps to

Crelate

Resume / File Attachment

1:1
Fully supported

Resume 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

maps to

Crelate

Job

1:1
Fully supported

Job 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

maps to

Crelate

Pipeline Stage

lossy
Fully supported

Applicant 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

maps to

Crelate

Activity (Email)

1:1
Fully supported

Email 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

maps to

Crelate

Activity (Call)

1:1
Fully supported

Call 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

maps to

Crelate

Note

1:1
Fully supported

Interview 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

maps to

Crelate

Job Distribution

1:1
Fully supported

Tracks 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)

maps to

Crelate

Custom Field (Person)

lossy
Fully supported

Custom 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)

maps to

Crelate

Custom Field (Job)

lossy
Fully supported

Custom 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

maps to

Crelate

Not Migrated

1:1
Fully supported

Scorecard 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

maps to

Crelate

Tag

1:1
Fully supported

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

Gotchas + challenges

What specifically takes care here

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 logo

Applicant Starter gotchas

High

No public API documentation or developer portal

Medium

Export requires a paid plan

Medium

No native bulk export endpoint

Low

Stage and tag schema varies per account

Crelate logo

Crelate gotchas

High

120 req/min API rate limit throttles bulk migrations

High

20 custom field per-entity cap forces data model decisions

Medium

15,000-record export ceiling on single operations

Medium

Sequences and automation workflows do not migrate

Low

API key is a querystring parameter, not a header

Pair-specific challenges

  • Applicant Starter has no public API documentation

    Applicant Starter does not publish API documentation on a public developer portal. We reverse-engineer endpoints by observing UI network traffic, which means any platform-side API change can break our connector without warning. We maintain a monitoring hook that alerts us when export requests return unexpected responses, but customers should be aware that migration timing depends on API availability and consistency. We verify API access during scoping by testing a read call against the Candidates endpoint; accounts without paid-tier access are flagged as export-ineligible.

  • Export requires a paid plan and iterates without bulk endpoint

    Applicant Starter's API is paginated and requires iterating through pages to retrieve all records. Large candidate databases require sequential API calls that consume time. We handle pagination automatically and throttle requests to avoid rate-limit triggers, but customers with thousands of records should plan for a longer migration window. Additionally, free or trial accounts have read-only UI access with no programmatic export capability; we verify paid-tier access during scoping before proceeding.

  • Pipeline stage names vary per account

    Applicant Starter allows user-defined stage names. One account might use Applied/Screening/Interview; another might use Open/Qualified/Closed. We extract the full stage schema during scoping and build a custom stage map to Crelate pipeline stages for each migration rather than applying a generic mapping. Stages with no direct Crelate equivalent require admin decision on replacement, which we surface during the mapping review phase.

  • Scorecard and evaluation data cannot export

    Scorecard data in Applicant Starter is stored in a proprietary format not accessible via the export API. We do not migrate scorecards as part of the standard scope. We document the location and format of any scorecard data during scoping and advise customers to perform a manual export of this data before migration. Scorecards can be rebuilt in Crelate using its custom form builder post-migration.

  • Activity timestamps may be incomplete for older records

    Some older activity records in Applicant Starter may lack complete timestamps. We flag records without timestamps during export and set a default date with a flag for admin review. We preserve as much temporal data as available and document gaps in the activity stream so that the customer understands which historical records have approximate dates.

Migration approach

Six steps for a successful Applicant Starter to Crelate data migration

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

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

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

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

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

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

Context on both ends of the pair

Applicant Starter logo

Applicant Starter

Source

Strengths

  • Low-cost entry point for small teams starting to formalize their hiring process
  • Clean, straightforward UI that requires minimal training
  • Built-in job board integrations covering major platforms like Indeed and LinkedIn
  • Automated candidate communication features including email templates and status notifications

Weaknesses

  • Limited API documentation and no public developer portal
  • No bulk export endpoint requires iterative API pagination
  • Export access gated behind paid tiers only
  • Custom pipeline stage schema varies per account, requiring custom mapping work
Crelate logo

Crelate

Destination

Strengths

  • Unified ATS and CRM in a single platform reduces data synchronization overhead for recruiting teams.
  • Fast setup with guided implementation reported as a significant time saver for small teams.
  • Transparent per-seat pricing without surprise fees at the base tier.
  • Flexible custom field configuration across core objects without developer dependency.
  • Export capability supports up to 15,000 records per operation for Contacts, Companies, and Opportunities.

Weaknesses

  • API rate limit of 120 requests per minute restricts bulk migration throughput.
  • Custom field cap of 20 per entity requires field consolidation for complex recruiting schemas.
  • All advanced features (Activities, Activity Forms, Core Record Field customization) are tier-gated add-ons.
  • Customer service responsiveness receives consistent negative feedback in reviews.
  • Resume parsing quality trails competitors and generates support requests.

Complexity grading

How hard is this migration?

Standard HRMS migration. 1 of 7 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Applicant Starter and Crelate.

  • Object compatibility

    B

    1 of 7 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    7-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Applicant Starter: Not publicly documented.

  • Data volume sensitivity

    B

    Applicant Starter doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Applicant Starter to Crelate migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Applicant Starter to Crelate data migrations

Answers to the questions buyers ask most during Applicant Starter to Crelate migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Most migrations land between two and four weeks for accounts under 5,000 candidates with straightforward stage schemas and no custom objects. Migrations with thousands of records, custom stage taxonomies, large resume libraries, or multi-year activity histories move to four to eight weeks because of iterative pagination handling, binary resume download and re-upload, and stage schema reconciliation. The timeline also depends on customer responsiveness during the scoping and test migration review phases.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Applicant Starter.
Land in Crelate, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day