Skip to content
Get a quote

Migrate to Crelate

Crelate is a combined ATS + recruiting CRM whose import model rewards teams that stamp External Primary Keys on day one, pre-create custom picklists and Workflow stages, and load Contacts before Jobs before Activities.

Short answer

FlitStack AI migrates employees, payroll, and benefits into Crelate from 200+ HR systems. Every field is mapped to Crelate's objects, history and associations come across, the Crelate setup is configured alongside, and the whole migration stays reversible in one click.

By

From Your system
DestinationCrelate
200+ sources mapped into Crelate

What Crelate supports, and where its import tools stop

  • 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.
REST onlyAPI key via querystring parameter
Rate limits120 req/min
ObjectSupportNote
ContactsfullContacts is Crelate's primary candidate and client record object. Standard fields include name, email, phone, and address. Custom fields are supported up to a 20-per-entity cap. We migrate Contacts with all custom property values and preserve linked Company and Opportunity associations via Crelate's lookup fields (Id, FirstName, LastName structure).
CompaniesfullCompanies represent client organizations and are a required dependency for many other objects. We import Companies first to ensure downstream Contacts and Opportunities can reference them correctly. Lookup fields to billing and primary contacts are preserved during migration.
JobsfullJobs represent job orders or requisitions. They link to the hiring Company and can have multiple associated Candidates and Placements. We preserve the Job-to-Company linkage and map pipeline stages to the destination's job workflow stages.
OpportunitiesfullOpportunities track revenue-generating business development activity in Crelate's CRM layer. They have a separate custom field allowance from Contacts and Companies. We map Opportunity stages and monetary fields directly to the destination's equivalent CRM object.
PlacementsmappedPlacements record placed candidates and capture salary, pay rate, start date, and fee percentage. They are derived from an existing Job and Candidate relationship. We migrate Placements only after confirming the parent Job and Contact records are present in the destination to avoid orphaned records.
Custom FieldsmappedCrelate supports custom fields on Contacts, Companies, and Opportunities with a documented cap of 20 per entity. We audit the customer's existing custom field inventory during scoping and flag any that exceed the cap or have naming conflicts in the destination. Fields are migrated as Short/Long Answer, Picklist, Date, or Numeric based on Crelate's field type metadata.
ActivitiesmappedActivities track recruiter tasks, calls, emails, and notes linked to Contacts and Companies. The Activities object is gated behind specific pricing tiers in Crelate. We verify the source plan includes Activity data before including it and map activity types to the destination's equivalent task or engagement object.
SequencesnoneSequences represent automated outreach workflows with templated tasks, emails, and text steps. Crelate stores Sequence definitions and enrollment state separately from contact records. We do not migrate Sequences as they encode platform-specific automation logic that cannot be reliably reproduced in other CRMs.
DocumentsmappedDocuments attached to Contacts, Companies, Jobs, or Placements are stored in Crelate's document management layer. We export documents via the API or bulk export tool and re-upload them to the destination with linkage to the matching parent record. Document metadata (file type, upload date, attached-by user) is preserved where supported.
TagsmappedTags in Crelate are label-based categorizations applied to Contacts, Companies, and Opportunities. We extract tags during export and apply them as tags or custom properties in the destination CRM depending on that platform's tagging model.
Users / OwnersmappedCrelate Users represent team members who own records. We map User records to Owner or Assignee fields in the destination, either by matching on email address or by creating new user accounts and establishing the mapping table. Inactive or archived users require explicit handling decisions.
Pipeline StagesmappedCrelate supports customizable pipeline stages for Opportunities and Jobs. Stage names and order are preserved in migration, but stage-specific automation (e.g., triggers that fire when a record moves to a stage) does not migrate and must be rebuilt in the destination.
Import / Export HistorynoneCrelate stores historical import logs that record when and by whom data was loaded. This metadata is not useful in a new system and is excluded from migration scope.

The Crelate migration guide

Why teams migrate to Crelate

The four shapes a Crelate migration takes, and what makes the platform easier — or harder — than the category average.

Crelate is a Talent Relationship Management platform paired with an Applicant Tracking System, positioned as a combined ATS + CRM for the recruiting and staffing market1. The product ships in two editions — Crelate Recruit for staffing agencies and Crelate Hire for in-house corporate recruiting teams — both sitting on the same underlying data model of Contacts, Companies, Jobs, Activities and Placements10.

The typical Crelate customer is a small-to-mid recruiting agency or in-house talent team — 5 to 150 recruiters — that wants a single system covering candidate search, client management, job-pipeline workflow and outreach without standing up a Bullhorn-scale admin function. Compared with Bullhorn, Crelate positions on lower setup cost and a faster time-to-productive; compared with Greenhouse or Lever, it positions on staffing-agency depth — Tearsheets, Client Portal, configurable Workflow stages and an ATS+CRM combined model12.

The shapes of migration that actually land on Crelate fall into four patterns. First, homegrown-database replacements — agencies moving off Access, Airtable or a bespoke SQL Server tool that grew beyond its limits. Second, legacy-ATS swaps, where the source is PCRecruiter, Avionté, JobAdder or a 1990s-vintage product whose data model and UI no longer fit modern recruiting9.

Third, Bullhorn or Greenhouse exits, where total cost of ownership or product fit drives the move and the source schema is rich but the entity model needs reshaping into Crelate's Contact-on-a-Job pattern. Fourth, M&A consolidation, where an acquired agency runs on a different ATS and the parent standardises on Crelate. Each shape has a different difficulty profile: a homegrown-database migration is mostly data cleanup; a Bullhorn migration is mostly entity-shape translation.

What makes migrating to Crelate easier than the category average is Import Data+, the native UI wizard that accepts XLSX and CSV, supports saved Field Maps for re-runs, and exposes a Preview / Invalid / Error Summary review step before any row commits29. The platform also offers a managed migration service operated by Crelate's own Professional Services team, with the explicit claim of having performed thousands of ATS migrations from 40+ source platforms10.

What makes it harder than the average is the External Primary Key model — Crelate's upsert key is a customer-set field that has to be populated on every source row before the first import, or every re-run inserts duplicates2. The picklist-internal-value distinction, Workflow Stage definitions, and ownership-versus-source-tracking field semantics all need explicit decisions before any row lands.

Custom reports, saved Searches, Workflow notification rules and email templates do not import — they are rebuilt from documentation. Teams that scope for that rebuild work up front finish on time; teams that assume parity do not.

Teams that scope for the rebuild work up front finish on time; teams that assume parity do not.

The Crelate data model you need to map into

Contacts, Companies, Jobs, Placements, Activities, Smart Tags — and the External Primary Key you'll wire on every record.

Crelate's ATS + CRM is built around a small set of recruiting-specific records, each with default and custom fields, and associations that connect them.

Before you can map a field on the source side, you need to know which destination record type the row belongs on, what fields it requires, and which value will serve as its upsert key. The table below summarises the core records you will touch.

ObjectWhat it storesRequiredTier
ContactCandidates, clients, hiring managers, vendors — every person recordFirst name, last name; Contact Type drives downstream viewsAll editions
CompanyClient companies, candidate employers, vendorsName; Company Type optional but drives filtersAll editions
JobOpen requisitions and pipeline records for recruiting workJob title, Company, primary recruiter (Owner)All editions
PlacementConfirmed hire / contract assignment outcomesContact, Job, Start date, Placement TypeCrelate Recruit primarily; Hire variant on Crelate Hire
Activity (Note, Call, Email, SMS, Task, Appointment)Engagement and audit timeline on every parent recordActivity Type, Activity Date, parent associationAll editions
Workflow StagePipeline position of a Contact on a Job (e.g. Submitted, Interviewing, Offer)Pre-created in Settings → Workflows; configurable per JobAll editions; up to 20 custom stages per Workflow132
Smart Tags / CategoriesSkills, industries, certifications, geographic specialtiesPre-created in Settings → Custom PicklistsMulti-value tag system across Contact, Company and Job
Resume / File AttachmentResume documents, contracts, signed offer lettersParent Contact + file binaryBulk resume import capped at 250 files per batch36

Crelate's upsert key is the External Primary Key — a customer-set text field on Contact, Company and Job that you populate from the source platform's primary key (or a UUID), then nominate as the identifier in the Import Data+ wizard so the import behaves as upsert rather than insert262. Without an External Primary Key, the importer falls back to a name + email heuristic that creates duplicates on re-run.

Plan for External Primary Key on day one: stamp the source primary key into every row before export, and use it on every subsequent re-run, reconciliation query and Activity association so updates are deterministic.

Custom fields in Crelate are configured under Settings → Custom Fields per record type. The catalogue below covers what you can model and the limits that apply72.

Field typeLimitNotes
Short Answer (text)Single-line textSearchable across the Advanced Search index94
Long Answer (text block)Multi-line textUse for paragraph-length notes, addresses, structured legacy text
Numeric / MonetaryNumber with optional currency formattingSupports range filters (e.g. salary range) in Advanced Search72
Date / Date-TimeStandard date or date + timeDrives Advanced Search Dates category; verify timezone handling per field
Picklist (Custom Picklist)Defined per field in Settings → Custom PicklistsInternal value vs display label distinction matters74
CheckboxBooleanSingle yes/no flag
Smart Tag (multi-value tag)Defined per tag categoryMulti-value; pre-create parent values to avoid silent drops
Lookup (record reference)Reference to another Crelate record by Id / NameLookups carry Id, FirstName, LastName triples — preserve all three on import30

Relationships in Crelate are modelled as lookups between records (Contact↔Company employment, Job↔Company, Job↔primary Recruiter) and as Workflow Stage memberships that place a Contact on a Job at a particular pipeline position132. Lookups round-trip as three-field objects with Id, FirstName and LastName; preserving all three on import is what keeps display strings correct in the Crelate UI30.

There is no native cascade-delete: deleting a parent Contact, Company or Job does not delete child Activities, Notes or Placements automatically. If your source platform relied on cascade behaviour, reproduce it via scripted cleanup.

Pre-migration prep — the work before you touch Crelate

What must be true on the source, the destination, and across the team before the first row hits Import Data+.

The single best predictor of a clean Crelate migration is how much work you do on the source side before the first Import Data+ button is pressed. Crelate's own guidance on ATS migrations explicitly calls out data quality, mapping clarity and customer responsiveness as the three variables that determine whether a project lands in two weeks or six135138.

The single best predictor of a clean migration is how much work you do before the first Import Data+ button is pressed.

Treat the source export as raw material that needs shaping to Crelate's expected formats — email lowercased, phone normalised, picklist values rewritten to destination Custom Picklist values, dates in MM/DD/YYYY or ISO-8601, owners resolved to Crelate usernames, and the External Primary Key stamped onto every row.

Source-side prep

  • Audit and dedup the source candidate database before export — email-case-only duplicates, role-based addresses and obviously stale records (last-touched 5+ years ago, never placed) should be pruned now, not after they land in Crelate66.
  • Stamp the External Primary Key on every Contact, Company and Job row in the source export. Use the source platform's primary key or a UUID and keep it stable across re-runs — this single value is what makes Import Data+ behave as upsert rather than insert262.
  • Normalise picklist values for Contact Type, Company Type, Job Status, Workflow Stage and every custom picklist — Crelate's Import Data+ matches on the value defined in Settings → Custom Picklists, and rows targeting undefined values are flagged in the Invalid Imports report rather than silently dropped6274.
  • Decide resume-file scope. Each candidate has zero, one or many resumes. Decide latest-only, all-versions, or none — the resume leg is its own pipeline that runs after Contact rows land, capped at 250 resumes per batch36139.
  • Convert source rich-text Notes to plain text ahead of time — Crelate Activity bodies do not preserve embedded images, charts or pasted Outlook HTML formatting reliably, so flatten or convert to Markdown before the load.

Destination-side prep

  • Stand up the Crelate account with the right edition — Crelate Recruit for agency workflows, Crelate Hire for in-house corporate recruiting. The two share the data model but differ on Job Portal, Client Portal and Placement workflows136.
  • Provision users first under Settings → User Roles, set the default recruiter role and create any custom roles before importing — owner assignment falls back to the import-running user when a referenced owner does not exist69104.
  • Pre-create every custom field in Settings → Custom Fields on the right record type with the right field type — Numeric, Date, Picklist and Long Answer have different downstream search behaviours and you cannot freely change type after the field has rows on it72.
  • Pre-create every Custom Picklist in Settings → Custom Picklists — every drop-down value that a source row targets must exist in the destination first, or the row appears in the Invalid Imports tab during preview6274.
  • Pre-build every Workflow in Settings → Workflows with the full stage list (capped at 20 stages per Workflow) before loading any Jobs or candidate-on-job records — Workflow Stage names are the field rows match against132.

People prep

Cutover only works if humans cooperate. Lock down a source-system freeze window — typically 24 to 72 hours for teams whose recruiters live in the system. Train recruiters on Contact search, Workflow Stage transitions and the Activity tab before go-live. A typical small-agency Crelate migration runs two to four weeks of elapsed time135138; data depth, custom-picklist count and resume volume drive the upper end. Crelate's own onboarding emphasises customer responsiveness as the largest single driver of project length137.

Import mechanisms: Import Data+ and bulk resume import

Two primary paths in, each with different limits and shapes. Picking the wrong one is how mid-migrations stall at scale.

Crelate exposes load paths that depend on dataset size and record-type mix. Import Data+ is the native UI wizard for spreadsheet loads. The dedicated Importing Resumes flow handles bulk resume parsing.

Import Data+

The native Import Data+ wizard lives at Menu → Import → Import Data from Excel32. It accepts XLS, XLSX and CSV files — colour fills, merged cells and pivoted layouts must be removed before upload33. The flow: pick the target record type, upload the file, accept or override the auto-mapping, nominate the External Primary Key column as identifier, save the Field Map for re-use, and step through Preview, Invalid Imports and Error Summary tabs before committing62.

The platform documentation states Import Data+ handles up to 50,000 records per spreadsheet import101. For datasets above that ceiling, split into multiple files. The Preview, Invalid Imports and Error Summary tabs are the single most-important quality gate in the wizard — a row that lands in Invalid Imports has failed validation, which is usually a custom-picklist value the destination does not recognise62.

Importing Resumes

Resume bulk import lives at Menu → Import → Import new Contacts36139. The wizard accepts up to 250 resume files at a time, parses each through Crelate's resume parser, and creates Contact records pre-populated with parsed name, email, phone, employment history and skill tags. You can apply tags, assign a Source, set the Owner and attach to a Job in the same step139.

The parser is the strength and the trap: on a clean account it dramatically reduces typing, but on a migration where you already have Contact rows in Crelate, parser-driven re-population can overwrite values you carefully migrated from the source. The pattern most teams use is: load Contacts via Import Data+ first with the External Primary Key, then attach resumes as binary attachments (no parser) keyed off the same External Primary Key.

Mapping your data into Crelate

The longest section — because field mapping is where almost every Crelate migration that fails actually breaks.

Mapping is where every ATS migration earns its scars. The schema decisions in your mapping spreadsheet determine whether recruiters find candidates on day two, whether placement reports work on day five, and whether the team trusts the data by day thirty.

Work record-type by record-type in strict import order: Companies first (so Contacts and Jobs can lookup against them), then Contacts (so Jobs can name a primary recruiter and Activities can attach), then Jobs (so candidate-on-Job rows can attach), then Workflow Stage assignments, then Placements, then Activities and Notes, and resumes and file attachments last.

Candidates — Contacts and the candidate database

The candidate database in Crelate is the Contact entity filtered by Contact Type. There is no separate Candidate object as in Bullhorn — the same record can be a candidate today and a hiring-manager client tomorrow, with Contact Type and Smart Tags driving the recruiter's view136140. The implication for mapping: source candidate and source contact tables both land on Contact, with Contact Type as the disambiguator.

Common source → Crelate Contact mapping
SourceDestinationNote
candidate_id / contact_idExternal Primary Key (upsert key)Stamp source primary key here; nominate as identifier in Import Data+62
first_name / last_nameFirst Name / Last NameRequired; preserve case as candidate-entered
emailEmailLowercase, trim, validate; not the primary upsert key in Crelate
phone / mobilePhoneCrelate does not enforce E.164; normalise upstream for Advanced Search94
candidate vs contact distinctionContact TypeDrives default views and dashboards — pre-create Contact Type values136
owner / recruiterOwner (User lookup)Map by username; unresolved owners default to the import-running user104
skills / tagsSmart Tags (Skill / Specialty categories)Multi-value; pre-create parent values in Settings → Custom Picklists
source / referral_sourceSource field + Source picklistDrives Advanced Search Past Activity filter94
gender / ethnicity / veteran / disabilityEEOC custom fields on ContactSensitive; confirm retention and consent policies first146

Companies and the client-side records

Common source → Crelate Company mapping
SourceDestinationNote
company_nameCompany NameRequired
company_idExternal Primary Key on CompanyUpsert key for cross-reference from Job and Contact
industryIndustry picklistPre-create values in Settings → Custom Picklists
company type (client / candidate-employer / vendor)Company TypeDrives default views in the Companies grid102
billing contactBilling Contact lookupResolves to a Contact record by name — load Contacts before this step30
parent / subsidiaryParent Company lookupRun as a second pass after all companies have External Primary Keys

Jobs, Workflow Stages and the candidate pipeline — the ATS deep dive

The job-requisition pipeline in Crelate is built around Jobs with Workflow Stages that hold candidate position in the pipeline132. A Job is the open requisition (e.g. Senior RN, Boston), and candidates move through pre-defined stages such as New Lead, Submitted, Phone Screen, Interview, Offer, Placed, Rejected. Crelate's Workflow stage cap is 20 stages per Workflow132.

Recreate every Workflow Stage in Settings → Workflows before loading any Job records. Rows that target an undefined Workflow Stage end up in Invalid Imports during the Preview step62. If your source pipeline has more than 20 stages, collapse adjacent low-volume stages into a single Crelate stage during transform — typical compressions merge Internal Review and Internal Submission into one bucket, or First Interview and Second Interview into a generic Interviewing stage.

Common source → Crelate Job + Workflow mapping
SourceDestinationNote
job_id / requisition_idExternal Primary Key on JobUpsert key; required for downstream candidate-on-Job rows
job_titleJob TitleRequired
client_idCompany lookup via External Primary KeyCompany row must exist first or the Job lookup fails30
primary_recruiterOwner (User lookup)Map by username; unowned Jobs default to import-running user
job_statusJob Status picklist (Open, Filled, Closed)Pre-create in Settings → Custom Picklists
candidate_on_job rowsCandidate-on-Job placement at Workflow StageMulti-step: supply Contact + Job + Stage Id together
stage_historySequence of Workflow Stage update events per transitionCrelate stage history is built by repeated updates, not by importing a history table

Application stage transition history is one of the most-asked-about pieces of an ATS migration and one of the least-supported on import. Crelate stamps stage-change history through repeated update events — there is no path to load a pre-built stage-history table directly. To preserve the timeline, capture each transition as (contact_id, job_id, stage, timestamp, user) and replay in date order, accepting that the modifying user will be the importing user, not the original recruiter.

Alternatively, store the legacy stage history verbatim in a Long Answer custom field on the Job-Contact join (or as a structured Activity Note) so the timeline stays searchable, and let live stage history accrue forward from cutover.

Interview feedback and Scorecards

Crelate Hire ships an Interview Loops & Templates feature where each interview step carries an assigned Scorecard with categorised questions and rating fields133134. Source scorecard data from Greenhouse, Lever or similar platforms does not map natively — the practical pattern is to land structured scorecard responses into a Long Answer custom field on the candidate-on-Job join (preserving the question / rating / interviewer triples as text), and to use Crelate's native Interview Forms going forward from cutover134.

If interview feedback is critical to search and reporting, pre-create the destination Question Categories under Interview Form Questions before the load so scorecard ratings can be replayed against the right category groupings134.

Candidate sources, EEOC and Smart Tags

Candidate source tracking in Crelate lives on the Contact's Source field plus an optional Source Type picklist, and feeds the Advanced Search Past Activity filter which is the primary reporting surface for source effectiveness94. Pre-create every source value (Indeed, LinkedIn Recruiter, employee referral, agency partner) in Settings → Custom Picklists, then resolve source labels to Crelate Source values via a lookup table during transform. Mismatched source labels appear as invalid rows during Preview62.

EEOC data (ethnicity, gender, veteran, disability status) lives on dedicated custom fields you create under Settings → Custom Fields on Contact. Treat EEOC fields as sensitive personal data: confirm the source export is permitted under your retention policy, that lawful basis exists under GDPR if any EU candidates are involved, and that the destination's privacy posture matches146147.

Smart Tags are Crelate's tagging system — Skills, Specialties, Industries, Certifications, Geographic specialties. They attach to Contact, Company and Job. Pre-create the Smart Tag categories and the parent values in Settings → Custom Picklists, then resolve source tag labels to Crelate tag values via a lookup table during transform. Smart Tag mismatches drop silently on import — verify against Custom Picklists, not against the Contact-record UI74.

Resumes and file attachments

Resume and attachment migration is its own pipeline that runs after Contact rows land. The Import Data+ wizard does not handle files; the supported paths are: (a) the Importing Resumes wizard, capped at 250 files per batch and parser-driven36139; (b) attaching each binary directly to a Contact with the External Primary Key as the key and parser re-population suppressed; and (c) the Crelate Chrome Extension and email-forwarding paths for self-service backfill101.

For large resume estates (tens of thousands of files), the pattern most agencies adopt is: keep originals in S3 or Azure Blob, load only the latest resume into Crelate with parser disabled, and store the archive deep link in a Long Answer URL custom field on the Contact. Confirm per-attachment file-type and size caps against the destination account configuration before the bulk run.

Notes, Tasks, Appointments and historical activity

Crelate supports Activities — Notes, Calls, Emails, SMS, Tasks and Appointments — with original timestamps preserved by setting the Activity Date field explicitly on creation. The Import Data+ wizard targets Contact, Company and Job rows; Activities must go through the Activity-aware variant of the import flow101. Each Activity row carries an Activity Type, body, Activity Date, owner, and one or more associations to parent records via External Primary Key102.

Activity bodies do not preserve rich-text formatting reliably — pasted Outlook HTML, embedded images and charts may render inconsistently. Convert source rich-text bodies to plain text or a Markdown-style structured format during transform, and keep the original rich-text body archived in S3 with a deep link in the Activity body if downstream search depends on it.

Custom-field mapping strategy

Resist the urge to map every source custom field one-to-one. Migrate only the custom fields used by an active recruiter workflow, Advanced Search or report in the last 12 months66. Excess fields weaken Custom Picklist governance, slow Advanced Search indexing, and make Crelate Reporting harder to wire.

For picklist fields whose source values do not match the destination, either: (1) extend the destination Custom Picklist with the missing values, (2) collapse adjacent values during transform, or (3) introduce a parallel Long Answer custom field holding the legacy value verbatim. Calculated / formula fields do not import — Crelate has no formula type, so source formulas must be replicated on each write or pre-computed before export72.

Audit trail, ownership and original timestamps

Crelate maintains an audit trail on the Activity tab of each Contact, Company and Job record, with the modifying user recorded as the user that initiated the change102. Activity Date on Notes, Calls, Emails, SMS, Tasks and Appointments can be set explicitly on creation — backdated Activities show up correctly on the timeline and the Advanced Search Past Activity filter94.

System-managed created-at and modified-at on Contact, Company and Job records cannot be overwritten on standard imports — they are stamped to import day. If you need to preserve the original audit trail, the pattern is to create Legacy Created Date and Legacy Modified Date custom Date fields on every record type and populate them from the source export. All historical-period reports should be wired against the legacy fields.

Owner assignment during import works only if the username exists at the moment of import; rows whose owner cannot be resolved are imported with the import-running user as owner, silently breaking per-recruiter Past Activity reporting104. Pre-provision every Crelate user account before the Contact, Company, Job and Activity loads.

The pitfalls that derail Crelate migrations

Specific failure modes — ranked by impact, each tied to the exact Crelate mechanism that breaks.

Validation and cutover

What to verify after the import job, in what order — and how to fail safely when something is wrong.

Validation is the bridge between Import Data+ finishing and recruiters being allowed in. A three-stage validation works best: a 10 percent pilot load with recruiter spot-checks, the full load with real-time row-count monitoring, and a 30-day audit driven by Advanced Search and Reporting125. The most reliable signal is recruiters verifying their own desks — they know what right looks like better than any reconciliation script.

Build a reconciliation queries spreadsheet that compares source and destination on each of these counts. Anything outside a 0.5 percent variance gets investigated before users get login access.

  • Total Contacts imported vs source — minus deliberately excluded rows (stale, opt-out, duplicate emails).
  • Total Companies imported vs source — checking that name-based collapse did not over-merge separate client records.
  • Total Jobs per status vs source, plus sum of Salary per Job Status — a non-trivial dollar variance signals a status-mapping error or a currency-precision drop.
  • Candidate counts per Workflow Stage per Job vs source — confirms the pipeline shape per requisition matches after stage compression.
  • Total Placements per Placement Type (Contract, Contract-to-Hire, Perm) and sum of Pay Rate per period — drives billing-side reporting from day one.
  • Activities per type (Notes, Calls, Emails, SMS, Tasks, Appointments) imported vs source — and a date-bucketed comparison to confirm Activity Date round-tripped.
  • Owner distribution per record type — group by Owner.username and confirm no record landed unowned that should not have104.
  • External Primary Key integrity — count distinct External Primary Keys per record type; any nulls or duplicates indicate the upsert key was not consistently set2.

On top of reconciliation, run a manual spot-check protocol: pick 30 random Contacts across Contact Types and verify each field against the source UI. Pick five high-value Jobs and trace the full association graph — Company, Owner, candidates at each Workflow Stage, recent Activities, Placement. If discrepancies show up in three or more of the 30, halt the load, fix the root cause, and re-run by External Primary Key upsert.

Crelate does not ship a native bulk-undo. The recovery path runs through Bulk Operations — multi-select on the Contact, Company or Job grid lets you mass-delete, mass-reassign, or mass-update by selection102. The practical rollback strategy: stamp every imported row with an Import Batch ID Long Answer custom field, and if catastrophe strikes, filter by that batch ID in the grid and bulk-delete the affected rows before re-running the load cleanly.

The other guardrails: export everything from Crelate to a backup file before the import starts (Crelate has no rollback button, so a self-managed backup is the only safety net), keep the source system live for at least 30 days post-cutover, and stage the Decommission of the source for 30 to 90 days out, never the same day.

Cutover sequencing: (1) source ATS goes read-only and the desk is notified; (2) a final delta export captures everything changed during the test window; (3) delta is loaded via Import Data+ against the External Primary Key; (4) reconciliation runs; (5) recruiters get login access and a 48-hour hyper-care window with the migration lead on call; (6) source decommission is scheduled 30 to 90 days out, never same-day.

Migration partners and tools

Crelate Professional Services, ETL vendors, specialist migration shops — what each is good for and how to choose.

Crelate's in-house Professional Services team operates migrations end-to-end from over 40 source platforms, with the explicit claim of thousands of completed ATS data migrations152137. The team handles export-side coordination, mapping, parser configuration and validation, and typically runs two to six weeks of elapsed time depending on dataset depth and customer responsiveness135138.

Crelate's published migration approach follows a Discovery → Development → Test pattern: a consultative scoping call, mapping development against the source export, and an iterative test cycle before the final cutover137. For agencies that want a hands-off migration with a single accountable team, Crelate Professional Services is the default path and is bundled into most subscription tiers as an onboarding-services line item152153.

On the ETL and iPaaS side, Fivetran, Airbyte, Workato and Integrate.io all have catalogues that include recruiting and CRM-adjacent connectors. None ship a first-class Crelate connector at the time of writing, so their role in a Crelate migration is the staging layer — landing source data into a warehouse (Snowflake, BigQuery), running SQL transformations to normalise picklist values and resolve owner usernames, then pushing into Crelate.

Workato and Integrate.io are the common picks where the migration is bundled with workflow automation rebuilds; Fivetran and Airbyte are the common picks for warehouse-first teams that want to reverse-ETL into Crelate.

Managed-migration cost ranges vary widely. A clean homegrown-database-to-Crelate load of under 25,000 Contacts with no resume backfill and standard fields only typically lands in the $2,000–$8,000 range as a Professional Services line item on top of the Crelate license, which starts at $119 per user per month153154. A Bullhorn-to-Crelate or Greenhouse-to-Crelate project with stage-history replay, custom fields, resume backfill at scale and Activity history typically runs $10,000–$40,000, driven by record count, Workflow stage compression depth and resume-file volume.

For teams that want to outsource the migration end-to-end, FlitStack specialises in ATS migrations into Crelate and handles the field mapping, External Primary Key design, Workflow Stage compression, resume-file pipeline, stage-history replay and validation work described in Sections 5 and 7. Pricing is fixed-fee, based on record count and source platform, with separate line items for stage-history replay and resume-file depth so the scope is transparent before signature.

This is one of several legitimate paths — the right choice for any given team depends on whether they want Crelate's own Professional Services bundled with onboarding, an iPaaS-first approach with Fivetran or Workato as the long-term sync layer, or a specialist migration vendor with platform-independent accountability. [Explore FlitStack →](/contact)

Crelate migration checklist

An eight-phase, task-by-task punch list for moving candidates, contacts, companies, jobs, placements, activities, and resume files into Crelate Recruit or Crelate Hire. Typical timeline: 4–12 weeks.

0. Decide & Plan9 tasks
  • Pick the Crelate edition: Recruit or Hire. Crelate Recruit targets staffing agencies and bundles CRM with ATS; Crelate Hire targets in-house corporate hiring. The edition choice changes which standard entities exist (Submission, Job Order, Placement vs. simpler Job + Application flow) and which add-ons apply.If skipped: Selecting the wrong edition forces a re-platform mid-project because the Job Order, Submission, and Placement objects only exist in Recruit.
  • Document in-scope object types. Decide explicitly which of Talent (candidates), Contact (clients), Company, Job, Placement, Job Order, Submission, Activity, Email, SMS, Task, and Note are part of the migration. Record each as in or out of scope.If skipped: Mid-project scope additions force re-running mapping, sandbox tests, and workflow design from the start.
  • Define historical-data scope per object. Decide how many years of activities, emails, SMS, notes, and stage transitions move across. Capture cut-off dates per object before the export work begins.If skipped: Without an explicit cut-off the export expands into a multi-year activity dump that no one budgeted for transforming.
  • Pick the Crelate plan and required add-ons. Confirm the chosen Recruit, Hire, or Connector tier and which add-ons (SMS, email tracking) are included.
  • Capture GDPR, residency, and retention obligations. Document the candidate-consent basis, retention windows, and right-to-erasure handling that apply to EEOC, source, and resume data once it lives inside Crelate. Crelate is SOC 2 audited and its underlying providers carry ISO 27001 and SOC certifications.If skipped: Legal blocks the import on go-live day when retention or candidate-consent review was not completed earlier.
  • Assign a single accountable migration owner (DRI). Name one person responsible for go/no-go on cutover. Document an escalation chain that includes recruiting leadership, IT, and (for Recruit) sales operations.
  • Set the cutover date and source-system freeze window. Choose a date that avoids client interview pushes, end-of-quarter placement reporting, and active candidate offer negotiations. Define the freeze window during which the source ATS goes read-only.If skipped: A cutover during an active interview week strands in-flight scheduling threads between two systems with no reconciliation path.
  • Document the migration success criteria in writing. List the row counts, pipeline-stage reconciliations, and recruiter-acceptance checks that must pass before the project is closed. Include the source-system decommission date.
  • List explicitly out-of-scope items. Examples: deactivated source users, legacy email-campaign analytics, archived job boards, expired offers. Capture them so they do not silently re-enter scope mid-project.
1. Pre-Migration Prep20 tasks
  • Run dedup on source candidate records using primary email as match key. Resolve duplicates in the source before export so two candidate profiles do not land as one Talent record in Crelate.If skipped: Duplicate source rows merge into a single Talent record and historical activity rows attach to the wrong person.
  • Run dedup on source company records using domain as match key. Normalize company names (Inc., LLC, Ltd. variants) before export. Crelate Companies link to Contacts and Jobs, so company duplicates propagate.If skipped: Two source companies for the same client create two Crelate Companies and split the placement history.
  • Standardize email casing, phone formats, and country codes on every contact row. Lowercase emails. Convert phone numbers to E.164 format. Standardize country names to ISO codes.
  • Identify candidate records missing required fields. Crelate Talent records typically require first name, last name, and either email or phone. Flag rows missing these and decide per row: enrich, drop, or accept as partial.If skipped: Rows missing required fields fail silently on Import Data+ and skew the validation row counts at the end.
  • Audit source resume files for orphaned or zero-byte attachments. Resume files referenced in the source database but missing from storage will fail to upload. Quarantine and document them before export.If skipped: Orphaned attachment references trigger thousands of import errors that mask real failures.
  • Export current record counts per object as a baseline. Capture row counts for candidates, contacts, companies, jobs, placements, activities, notes, emails, and SMS. This becomes the reconciliation baseline in Phase 6.If skipped: Without a baseline, no one can prove whether the migration lost records.
  • Decide an External Primary Key value for every Talent, Contact, Company, and Job record. Crelate supports an External Primary Key on import to allow idempotent re-runs and avoid duplicates. Pick a stable identifier from the source system (e.g. source-system record ID) and stamp it on every export row.If skipped: Without an External Primary Key, every re-run of an import wizard creates duplicate Crelate records.
  • Provision the Crelate tenant on the chosen edition. Activate Crelate Recruit or Crelate Hire. Confirm seat count covers every recruiter, sourcer, coordinator, and admin who will work in the system on day one.
  • Configure organization-level settings (timezone, default currency, locale). These settings drive how dates and currency render across the UI and on imports. Set them before any data load.If skipped: Loading activity timestamps before fixing the org timezone shifts every activity by hours and is painful to correct.
  • Create every required user account in Settings | Users and assign a User Role. Default users land in the Recruiter role. Custom user roles are a Business-tier feature; on Professional you can still modify the default roles. Provision users before importing records so ownership lookups resolve.If skipped: Importing records with owner references to users that do not yet exist forces the owner to fall back to the migration service account.
  • Build every Custom Picklist in Settings | Custom Picklists. Picklist values must exist before any record references them. Create the values for source, candidate status, employment type, and every other dropdown your mapping spreadsheet needs.If skipped: Importing a picklist value that does not exist drops the value silently or rejects the row.
  • Build every custom field in Settings | Custom Fields against the right entity. Crelate supports Short Answer, Long Answer, Date, Numeric, Picklist, and other custom field types on Contacts, Companies, and Jobs. Create each as the correct type before import; types cannot be changed after data exists.If skipped: Loading data into a custom field that does not exist drops the values entirely.
  • Build Workflows and Workflow Stages per job category, respecting the 20-stage cap. Crelate caps Workflow Stages at 20 per workflow. Design the destination pipeline to fit under the cap before mapping source stages.If skipped: Source pipelines with 25–30 stages collapse unpredictably if the consolidation strategy is decided on import day.
  • Create Smart Tag categories that the import will populate. Smart Tags act as folksonomic categorization across Talent and Contact records. Plan the tag taxonomy before import so tags do not multiply uncontrolled.
  • Configure Email and SMS templates that recruiters will need on day one. Submittal templates, candidate-outreach templates, and interview-confirmation templates need to exist before Bulk Submit to Job operations can run.
  • Pause every active integration on the Crelate side. Pause job-board distributors, calendar sync, and email sync until cutover so test loads do not blast notifications to candidates and clients.If skipped: A test load with sync enabled fires hundreds of real interview invites to candidates.
  • Stand up a clean sandbox-equivalent: a separate Crelate test organization mirroring production config. Crelate does not provide a built-in sandbox-clone like enterprise CRMs; a fresh trial or test tenant configured identically serves the same purpose. Mirror every picklist, custom field, and workflow stage before loading sample data.If skipped: Testing in production pollutes the live tenant and forces a bulk-delete cleanup before go-live.
  • Communicate the source-system freeze window to every recruiter and coordinator. Define the exact start time. Recruiters must stop creating or updating records in the source ATS from this moment.If skipped: Late edits in the source after the export create a silent delta that will never reach Crelate.
  • Schedule role-based training sessions on Crelate basics. Run separate sessions for recruiters, sourcers, coordinators, and account managers. Cover the Activity Stream, Smart Tags, candidate stage moves, and Bulk Operations.
  • Designate a first-responder team for the first 48 hours post-cutover. Name two recruiters plus the migration DRI as first responders. Publish the channel they monitor.
2. Source Export13 tasks
  • Export every Talent (candidate) record with all standard and custom fields. Export to CSV or XLSX. Include source-system ID, first name, last name, every email, every phone, address, current title, current company, source, owner, and every custom field.If skipped: A missed custom field surfaces in Phase 6 when a recruiter cannot find the data they relied on.
  • Export every Contact (client) record with all fields. Include the company link, role/title, every email, every phone, and the owning recruiter or account manager.
  • Export every Company record with all fields. Include domain, address, parent/child company link, owner, every custom field, and the contract status if present.
  • Export every Job (and Job Order, if Recruit) record. Include the company link, hiring-manager contact link, owner, workflow stage at export time, status, location, employment type, and every custom field.
  • Export every Placement record (Recruit edition). Placements link a Talent, a Job, a Company, dates, fee, and pay rate. Export the full row plus the relationship keys.If skipped: Placements rebuilt without the original fee and start-date columns break commission reporting.
  • Export the candidate-to-job pipeline associations with stage history. For each candidate-on-job record export the current workflow stage, the prior stages, and the timestamp of every stage transition. This is the raw data for Phase 3's stage-history reconstruction.If skipped: Without stage-transition timestamps the time-to-hire reports in Crelate restart from cutover.
  • Export activities, notes, calls, emails, and SMS as separate files. Each activity type typically has its own schema. Capture the original timestamp, owner, body, and the foreign keys to candidate, job, contact, and company.
  • Export resume and attachment binaries together with the metadata index. Pull the binary files plus a CSV that maps each file to its source candidate ID, original filename, content type, and upload timestamp.If skipped: Pulling binaries without the metadata index makes it impossible to re-attach files to the right Talent record.
  • Export the source user list with email, role, and reporting structure. This becomes the input for Crelate user provisioning and owner-mapping in Phase 3.
  • Export pipeline / workflow / stage definitions from the source. Capture every source workflow including hidden, archived, and per-client variants. These are inputs for the 20-stage Workflow design in Crelate.
  • Export source EEOC and self-identification fields separately, gated by access. EEOC fields carry stricter handling rules. Export to a separate file and store with restricted access during the migration.If skipped: EEOC fields exported into the main candidate CSV bypass access controls and create a compliance incident.
  • Capture screenshots and config exports of source dashboards, reports, and automations. Reports, dashboards, automated workflows, and email templates rarely migrate cleanly. Snapshot them so they can be rebuilt manually in Crelate.
  • Document the exact UTC timestamp of every export file. Name files with the timestamp. This is the baseline for the cutover delta in Phase 5.
3. Transform & Map21 tasks
  • Build a master mapping spreadsheet keyed by source field. For every source field record: destination Crelate entity, destination field, field type, transformation rule, nullability, and whether the field is required on import.If skipped: Without a centralized mapping document, each engineer interprets ambiguous fields differently and the data lands inconsistently.
  • Resolve every picklist value mismatch against Crelate Custom Picklists. List source picklist values, list destination picklist values, and decide a mapping for each. Where source has values the destination should not carry, decide drop vs. merge.If skipped: Unmapped picklist values silently drop on import or fall back to the destination default.
  • Pick the External Primary Key column per object. Crelate's Import Data+ supports an External Primary Key for idempotent upsert. Choose the source-system ID column for Talent, Contact, Company, and Job and document the choice.If skipped: Re-running an import without an External Primary Key set duplicates every record.
  • Decide per object the unmapped-field strategy. For source fields with no Crelate equivalent decide: drop, concatenate into a Note, or create a custom field. Document the choice per field.
  • Save the Import Data+ field map for repeated runs. Once mapping in Import Data+ is configured, save it via the cogwheel | Save Mappings. Name the saved map per object so sandbox and production runs reuse the same configuration.
  • Convert every date and timestamp to the format Import Data+ accepts. Crelate's import expects ISO-style dates. Normalize US-format dates, locale variants, and Excel date serials before producing the import file.If skipped: Mixed date formats cause silent month/day swaps that are not discovered until reports run.
  • Re-encode every text field as UTF-8. Source exports from older systems often arrive as Latin-1 or Windows-1252. Re-encode to UTF-8 to avoid mojibake on candidate names, addresses, and notes.If skipped: Non-UTF-8 encoded names import as garbled characters and require row-level cleanup post-cutover.
  • Truncate or split fields that exceed Crelate's character limits. Long Answer fields accept significantly more text than Short Answer. Audit source string lengths, route long values to Long Answer fields, and split where the source exceeds even the long limit.
  • Strip or escape characters that break Import Data+ parsing. Quote characters, newlines inside cells, and stray commas in unquoted CSVs all break row alignment. Use proper CSV quoting and confirm a small sample parses cleanly before scaling.If skipped: A single mis-quoted row shifts every subsequent column for thousands of rows.
  • Normalize phone numbers and emails to one row per channel. Crelate stores multiple emails and phones per record. Decide which source column maps to Primary vs. additional, and prevent the same value from landing twice.
  • Confirm the file is saved as .xlsx, .xls, or .csv with no cell coloring or merged cells. Crelate's spreadsheet import troubleshooting calls out unsupported coloring, merged cells, and non-spreadsheet file types. Strip formatting before upload.If skipped: Formatted cells cause the entire upload to reject with a generic error.
  • Decide and implement the historical-timestamp strategy per object. Crelate's import re-stamps Created and Modified to the import date. Where the original date matters, route it to a custom date field (e.g. 'Source Created On') so it survives. Document the choice for each object.If skipped: Without a custom date field, every record's true created-on is lost and reports look like all data is brand new.
  • Decide and implement the record-ownership strategy. Best-match owners by email to the provisioned Crelate users. Where the original owner has no Crelate user, route to a single migration service account and tag the record with a custom 'Original Owner' field.If skipped: Without an Original Owner backup field, recruiters lose visibility into who handled the candidate previously.
  • Decide the resume / file attachment strategy. Resumes upload through the bulk Importing Resumes wizard (up to 250 files per batch with parsing) or via parser-disabled attachment paths that bypass re-parsing. Decide per file category which path applies.If skipped: Routing pre-parsed resumes through the parsing wizard re-parses already-clean data and overwrites fields with parser output.
  • Build Talent records and resume-file pairings using the 250-file bulk wizard for parser-driven loads and parser-disabled attachment paths for already-clean data. Crelate's bulk resume importer accepts up to 250 resumes per batch and creates Talent records via the parser. For pre-cleaned data where the source already has parsed fields, attach the binary with the parser disabled so existing field values are not overwritten.If skipped: Mixing parser-driven and parser-disabled loads on the same Talent batch overwrites mapped fields with re-parsed values and silently corrupts clean source data.
  • Map the source Job-to-Stage-to-Placement pipeline to Crelate's Job → Workflow Stage → Placement structure within the 20-stage cap. List every source pipeline stage. Group them into the 20-stage Crelate workflow per job category. Where the source has more than 20 stages, decide which stages collapse and document the merge. Reserve a final stage for Placement creation.If skipped: Skipping the 20-stage planning step forces a last-minute stage collapse that destroys time-in-stage reporting.
  • Populate the candidate Source field plus Smart Tags from source source-tracking fields. Crelate's Source field is a picklist on the Talent record. Smart Tags layer on top for folksonomic categorization. Decide which source attributes map to Source (single-value), which map to Smart Tags (multi-value), and pre-create Smart Tags before import.If skipped: Pushing free-text source values straight into the Source picklist creates dozens of one-off picklist entries that the Past Activity filter cannot meaningfully query.
  • Create EEOC custom fields under Settings | Custom Fields with restricted role-level access and an explicit retention note. Self-identification, veteran status, disability, race/ethnicity, and gender each get their own custom picklist on the Talent record. Restrict edit access to compliance-eligible roles. Document the retention window per field aligned to GDPR and local rules.If skipped: Loading EEOC values into open custom fields exposes self-identification data to every Crelate user and creates a compliance incident.
  • Configure Interview Loops & Templates plus Scorecards, and route unmapped scorecard fields to a Long Answer fallback. Interview Loops & Templates carry the interview sequence per job. Scorecards capture per-interviewer ratings against question categories. Source scorecard data without a clean equivalent in Crelate's Interview Form Questions schema lands in a Long Answer custom field on the candidate-on-job record so the history survives.If skipped: Dropping unmappable scorecard answers loses the interview-decision audit trail and forces hiring teams to relitigate prior decisions.
  • Replay application stage-transition history in chronological order. Crelate's Activity Stream records stage moves as activities. Replay each historical transition from oldest to newest, using the External Primary Key so the move attaches to the right candidate-on-job record. Filter out internal-only stage hops if the team agrees they pollute the stream.If skipped: Bulk-loading current stages without replaying transitions strips the Past Activity filter of any candidate history and breaks time-to-hire reporting from day one.
  • Decide handling for client-portal candidate submissions. The Crelate Client Portal lets clients review submitted candidates in real time. Decide whether historical client decisions move across as Activity Stream entries, as Notes, or are left in the source archive.
4. Sandbox Test Migration12 tasks
  • Load a 1–5% representative sample of each object into the test tenant. Use Import Data+ for spreadsheet objects and the appropriate binary-upload path for attachments. Cover every custom field, every workflow, and every owner mapping at least once.
  • Inspect 10 random Talent records field-by-field against the source. Open each in Crelate. Compare every standard field, every custom field, every Smart Tag, the Source picklist, and the resume attachment against the source record.If skipped: Skipping the manual spot-check lets a systematic mapping error reach production undetected.
  • Test edge-case strings: long Long Answer values, accented names, embedded quotes, embedded newlines. Confirm Crelate stores the value intact in each case. Confirm display, edit, search, and Advanced Search behavior on the imported value.
  • Test relationship loads: Talent→Job links, Talent→Company links, Job→Contact (hiring manager) links. Confirm each association resolves the right parent via External Primary Key, not by Crelate-assigned IDs that change between tenants.If skipped: If lookups resolve by Crelate ID rather than External Primary Key, every production run will mis-link records.
  • Test the Importing Resumes wizard with a 250-file batch. Confirm the parser creates Talent records correctly, that the resume attaches to the right candidate, that Smart Tags apply, and that the assigned Source and owner stick.
  • Test the parser-disabled attachment path. Confirm the file attaches to the right Talent (matched by External Primary Key) without re-parsing and without overwriting field data.If skipped: If the parser flag is wrong, a production run will overwrite clean field data with re-parsed text from the resume.
  • Test the stage-transition replay sequence on a single job. Replay 10–20 historical transitions for one job in chronological order. Open the Activity Stream and confirm the transitions render with correct timestamps and stage names.
  • Test the Past Activity filter on a sample of migrated candidates. Filter candidates by Past Activity to confirm historical Activity Stream rows surface in Advanced Search. If they do not, the timestamp or owner mapping is wrong.If skipped: Past Activity filter blindness post-cutover destroys nurture and re-engagement workflows.
  • Run a full-volume timed test on the largest object. Time the load. Extrapolate to the full record count. Confirm the projected run fits inside the cutover window.If skipped: Discovering on cutover night that the load will take 18 hours instead of 4 forces an emergency reschedule.
  • Capture every Invalid Imports row and every Error Summary entry from Import Data+. Import Data+ surfaces Preview, Invalid, and Error Summary tabs. Resolve every Invalid row and every Error Summary entry before declaring the test successful.
  • Have a recruiter and an account manager (or hiring manager, on Hire) spot-check the test tenant. Walk them through a real candidate workflow against migrated data. Their feedback is the most reliable signal that the schema works.
  • Get written sign-off on the sandbox test results before Phase 5 begins. Document the test results, known issues, and accepted residual risks. Get the DRI's signature.If skipped: Proceeding to production without sign-off transfers risk to whoever runs the cutover at 2am.
5. Production Cutover11 tasks
  • Confirm the source-system freeze is in effect and verify no writes in the last hour. Pull the latest activity log from the source. Confirm zero new or modified records since the freeze start.If skipped: Late writes after the export create a silent delta that never reaches Crelate.
  • Take a final full export of source data to capture the delta from Phase 2. Re-export every object so the production load uses the freshest data. Stamp the new export files with the cutover UTC timestamp.
  • Pause every Crelate integration, automated email, and SMS template firing. Confirm job-board distributors, calendar sync, email sync, and outbound SMS are paused so the load does not notify candidates and clients.If skipped: Enabled integrations on import day blast hundreds of duplicate interview invites to candidates.
  • Load objects in strict dependency order. Order: users → Companies → Contacts → Jobs (and Job Orders) → Talent → Talent-Job pipeline associations → Activities/Notes/Emails/SMS → resume binaries and other attachments → Placements.If skipped: Loading Jobs before their parent Companies forces re-parenting cleanup and leaves orphans.
  • Use the External Primary Key for upsert on every import. Every Import Data+ run uses the External Primary Key as the match key so re-runs do not duplicate.If skipped: A re-run without the External Primary Key set creates a second copy of every record.
  • Capture import job IDs, row counts, error logs, and Error Summary entries for every load step. Save them to a single cutover log. Cross-reference against the Phase 2 baseline.
  • Cross-check destination row counts against source row counts at each step. Confirm parity before moving to the next object. Stop and diagnose any unexpected delta greater than 0.1%.If skipped: Pushing through despite an unexplained delta hides a systematic loss until validation.
  • Run the stage-transition replay job. Replay historical stage moves in chronological order. Confirm the Activity Stream populates correctly on a 10-record sample before continuing.
  • If any load step fails partway: stop, diagnose, fix the transform, and re-run idempotently. Do not push through with partial data. The External Primary Key upsert pattern means a re-run is safe.If skipped: Pushing through with partial data forces a Bulk Operations rollback that may not catch every malformed row.
  • Re-enable integrations, sync, and outbound channels only after every load completes and counts reconcile. Bring integrations back online in a controlled order: email sync first, then calendar, then SMS, then job-board distribution.
  • Lock the source system to read-only. Disable every user account's write permission in the source ATS now. Announce the read-only date to recruiters.If skipped: Leaving the source writable invites a recruiter to update a record there and forget to repeat the change in Crelate.
6. Validate19 tasks
  • Compare total record count per object against the Phase 1 baseline. Talent, Contact, Company, Job, Job Order, Placement, Submission, Activity, Email, SMS, Note, and resume-attachment counts. Investigate any unexplained delta.If skipped: An unexplained delta on Talent count usually masks a duplicate-merge bug or a silently dropped picklist value.
  • Compare active-candidate count (the ATS-relevant aggregate) by stage. For each Workflow Stage compare the source count and the Crelate count. Stages with deltas reveal stage-mapping errors.
  • Compare active-job count by workflow. Confirm open job count matches source. A missing job leaves candidates orphaned.
  • Cross-check 25–50 random Talent records field-by-field against the source. Cover every custom field, every Smart Tag, the Source picklist, and the resume attachment.If skipped: Sample-based validation catches systematic mapping errors that aggregate counts miss.
  • Verify every Custom Picklist value present on imported records exists in Settings | Custom Picklists. Any picklist value not in the official list silently drops. Confirm none did.
  • Verify Talent→Job pipeline associations on a sample of 25 candidates. Each candidate should appear on the correct job(s) in the correct workflow stage.If skipped: Mis-linked candidate-on-job records show up to recruiters as 'where did this candidate go?' on day one.
  • Verify Contact→Company links on a sample of 25 contacts. Each contact should appear under the correct Company.
  • Verify Job→Hiring Manager Contact links. Each open job should resolve to a hiring-manager Contact via the correct Company.
  • Verify Activity Stream entries attach to the correct Talent, Job, Contact, and Company. Spot-check 20 candidates with rich activity history. Confirm activities, emails, and SMS render in the correct context with the correct historical timestamps.If skipped: Activities attached to the wrong record produce confusing recruiter experiences and false 'last-contacted' dates.
  • Verify resume files are accessible and linked to the correct Talent record. Download a sample of 25 resumes and confirm the file matches the expected candidate.
  • Verify Placement records link the correct Talent, Job, and Company with the correct fee and dates. Spot-check 20 Placements. This is the highest-revenue object in Recruit; errors here distort commission calculations.If skipped: Placement-mapping errors silently distort commission and revenue reports for months.
  • Confirm the historical-timestamp strategy worked. Open 20 records and confirm the original created/modified date lives in the documented custom date field (per Phase 3c).If skipped: If the original timestamps did not land, the Past Activity filter cannot date-range historical engagement.
  • Confirm EEOC fields are populated and visibility is restricted to compliance roles. Open a non-compliance-role test account and confirm EEOC fields do not render.If skipped: EEOC visibility leaks are a regulator-reportable incident in many jurisdictions.
  • Capture a SOC 2 / GDPR evidence pack of the migration run. Snapshot import job logs, error summaries, retention configuration, and access-control settings to a controlled folder.
  • Have 3–5 power-user recruiters validate their day-to-day workflows. Cover sourcing through Bulk Operations, candidate stage moves, interview scheduling via Interview Loops, scorecard logging, and submittal to client (Recruit edition).If skipped: Skipping power-user validation lets day-to-day workflow gaps surface post-launch when there is no time to fix them.
  • Have an account manager (Recruit) or hiring manager (Hire) validate the client-facing flow. Recruit: walk a real candidate through Bulk Submit to Job and confirm the Client Portal renders correctly. Hire: walk an open requisition through an interview loop end-to-end.
  • Run the Advanced Search Past Activity filter against the migrated dataset. Confirm a query for 'candidates contacted in the last 12 months' returns the expected count when timestamps are preserved per Phase 3c.
  • Document every data issue raised during user-acceptance. Capture severity (blocker / cosmetic), affected count, owner, and remediation date.
  • Get written sign-off from the migration sponsor before Phase 7 begins. Capture the sponsor's signature, the residual-issue list, and the agreed remediation timeline.
7. Post-Migration Cleanup11 tasks
  • Send go-live communication to every recruiter, sourcer, coordinator, and account manager. Include the Crelate login URL, the first-responder contact, the known-issue list, and the source-system read-only date.
  • Run role-based training sessions in the live Crelate tenant. Separate sessions for recruiters, sourcers, coordinators, and (Recruit) account managers. Cover Advanced Search, the Past Activity filter, Smart Tags, Bulk Operations, and Interview Loops.
  • Set the source ATS to read-only and announce the read-only date. Confirm every source user account is in a read-only role. Document the date and post it where the team will see it.
  • Rebuild reports in Crelate. Source reports rarely migrate. Recreate the top recruiter scorecards, time-to-hire, submittal-to-hire, and placement-revenue reports using Crelate's reporting and Power BI integration.
  • Rebuild automated workflows, email templates, and SMS templates. Recreate auto-tag rules, candidate-acknowledgement emails, submittal templates, and interview-confirmation SMS templates. Test each end-to-end before turning it on.If skipped: Re-enabling an untested template can fire a malformed email to thousands of candidates.
  • Re-establish every external integration. Calendar sync, email sync, job-board distributors, background-check vendors, e-signature vendors, and the Sourcing browser extension. Test each connection.
  • Install and configure the Sourcing browser extension for every recruiter. The Sourcing extension lets recruiters capture candidates from LinkedIn and other web sources directly into Crelate. Roll out to every recruiter and confirm sign-in works.
  • Schedule a 30-day post-migration retrospective. Cover what went well, what didn't, and the residual-issue burn-down progress.
  • Decide and document the source-system decommission date. Typically 90 days after cutover, after the final retention window. Record the date and the data-archive plan.
  • Archive the source-system exports and the cutover log to long-term storage. Encrypt at rest. Restrict access to compliance and the migration DRI. Record the retention window per regulatory requirement.If skipped: Without an archived source dump, a later forensic question (e.g. 'what did this candidate's record look like in 2024?') is unanswerable.
  • Close out the migration project formally. Final status report, lessons-learned document, residual-issue handoff, and project closure note.

Questions, answered

Migrating to Crelate: questions

How long does migration to Crelate take?

A small-agency migration with under 5,000 Contacts on standard fields runs three to five business days of elapsed Import Data+ work. A mid-size project with Workflow stage compression, custom fields, resume backfill and Activity history runs two to six weeks, including prep, dry runs, validation, training and hyper-care.

Can I migrate from Bullhorn to Crelate?

Yes — Bullhorn-to-Crelate is one of the more common staffing migrations. Bullhorn's Candidate, ClientContact and ClientCorporation entities consolidate into Crelate Contacts disambiguated by Contact Type. JobOrder and JobSubmission collapse into Crelate Jobs with Workflow Stages. Plan for stage compression and externalID-to-External-Primary-Key remapping during transform.

Can I migrate from Greenhouse or Lever to Crelate?

Yes, but Greenhouse and Lever use pipeline-per-job models with many interview-stage subdivisions that exceed Crelate's 20-stage Workflow cap. Plan for stage compression on every requisition, scorecard data landed into Long Answer fields, source-tracking values mapped to Crelate Source picklists, and EEOC fields confirmed against retention policy before export.

Does Crelate preserve original timestamps on import?

Partially. Activity Date on Notes, Calls, Emails, SMS, Tasks and Appointments can be set explicitly and survives correctly on the timeline. But system-managed created-at and modified-at on Contact, Company and Job records cannot be overwritten on standard imports — use Legacy Created Date custom fields instead.

Can I migrate custom fields and picklists into Crelate?

Yes — pre-create every custom field under Settings → Custom Fields and every picklist value under Settings → Custom Picklists on the right record type before importing. Calculated and formula fields do not import because Crelate has no formula type; replicate them on write or pre-compute before export.

What happens to candidate stage history during a Crelate migration?

Crelate exposes no path to upload a pre-built stage-history table. The audit trail is built by repeated update events that each generate a history row, so preserving the original timeline means replaying each transition in date order — or storing legacy history verbatim in a Long Answer field.

Is there an undo or rollback for Crelate imports?

There is no native bulk-undo. Stamp every imported row with an Import Batch ID custom field and bulk-delete by that field via Bulk Operations on the grid if recovery is needed. Export everything to a backup file before the import starts — that self-managed export is your only true safety net.

Sources

  1. Crelate platform overview
  2. Import Data+ — Crelate, Inc. Help Center
  3. What is an ATS Data Migration? — Crelate
  4. Crelate Professional Services — Customer Success
  5. Crelate Recruit — Client Portal for Recruiters
  6. Crelate Developer Guide — Crelate Help Center
  7. Import Data+ — Beginning your Import
  8. Spreadsheet Import Troubleshooting — Crelate Help Center
  9. Importing Resumes — Crelate Help Center
  10. Import Data+ — Mapping, Identifier and Reviewing your Import
  11. Data Cleanup Best Practices (BEFORE IMPORT) — HubSpot Community
  12. User Roles — Crelate Help Center
  13. Best Practices: Custom Fields — Crelate Help Center
  14. Using a Picklist in Crelate — Crelate Help Center
  15. Advanced Search — Crelate Help Center
  16. Master Guide — Importing Data — Crelate Help Center
  17. Bulk Operations — Crelate Help Center
  18. Assigning Record Ownership — Crelate Help Center
  19. Post-Migration Validation and Optimization Guide — Microsoft Learn
  20. Creating your Workflow Stages — Crelate Help Center
  21. Interview Loops & Templates — Crelate Help Center
  22. Interview Form Questions — Crelate Help Center
  23. ATS Data Migration Best Practices — Crelate
  24. Crelate Recruit edition — Client Portal and Contact Types
  25. Don't Let Fear Stop Your ATS Data Migration — Crelate
  26. The Recruiters Guide to ATS Data Migrations — Crelate (PDF)
  27. Importing Resumes — bulk import up to 250 at once
  28. ATS Data Migration definition and process — Crelate
  29. Security Policy — Crelate (SOC1/SOC2, HIPAA, ISO27001)
  30. What rules apply if my organisation transfers data outside the EU? — European Commission
  31. Crelate Professional Services — migration developers
  32. Crelate Pricing 2026 — TrustRadius
  33. Crelate Software Pricing, Alternatives & More 2026 — Capterra

Get a quote

Moving to Crelate?

Tell us where your data lives today and roughly how much there is. We scope the migration and the Crelate setup with you, then send a quote.

Get a quote