Crelate to Bullhorn ATS & CRM migration
We migrate Candidates, ClientContacts, ClientCorporations, Jobs, and Placements from Crelate into Bullhorn with the staffing data model compressed upfront, custom fields prioritized against the 20-per-entity cap, and every Placement dependency resolved before cutover so your recruiters find their submission history intact on day one.
FlitStack AI migrates candidates, clientcontacts, clientcorporations, joborders and placements from Crelate to Bullhorn ATS & CRM, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 2-4 weeks.

What moves from Crelate to Bullhorn ATS & CRM?
Moving from Crelate to Bullhorn is a data-model compression migration disguised as a vendor switch.
Read the full summary
Crelate runs a unified ATS+CRM schema where Contacts, Companies, Jobs, and Opportunities share a flat structure; Bullhorn uses a deeply relational staffing model with separate Candidate, ClientContact, ClientCorporation, JobOrder, JobSubmission, and Placement objects that encode the full recruiting lifecycle. We resolve the schema expansion during scoping, map Crelate's unified contact records to Bullhorn's Candidate (for job seekers) and ClientContact (for employer contacts) objects, and sequence Placements last so that their parent JobOrder and Candidate references exist first. Crelate's 20 custom field per-entity cap forces a field prioritization exercise before any data moves; we surface that during discovery rather than mid-migration. Bullhorn's module-based pricing (reporting, support, automation) adds separate line items beyond the base per-seat rate, which we disclose during scoping so the destination cost reflects the full contract. Sequences, automations, and Crelate's Activity add-on tiers do not migrate; we deliver a written map for Bullhorn rebuild.
Contact (candidate records) → Candidate
Crelate Contacts where the record type indicates a job seeker map to Bullhorn Candidate.
How it maps
We identify candidate records by examining Crelate's contact type property, tag assignments, and job submission history. Standard Candidate fields (firstName, lastName, email, phone, address) map directly. The original Crelate contact ID is preserved in a customText field for reconciliation. If Crelate's Activities module is enabled, candidate notes and tasks migrate as Bullhorn Note and Task records linked to the Candidate entity.
Contact (employer contacts) → ClientContact
Crelate Contacts associated with Companies that represent employers map to Bullhorn ClientContact.
How it maps
The mapping resolves the ClientContact's clientCorporation reference to the migrated ClientCorporation record by matching on company name or Crelate company ID. ClientContact fields (firstName, lastName, email, phone, title) map directly. Custom fields on Crelate employer contacts migrate to ClientContact custom fields if under the 20-field destination cap.
Company → ClientCorporation
Crelate Companies map to Bullhorn ClientCorporation.
How it maps
This is the first object imported because ClientCorporation is a required dependency for JobOrder, ClientContact, and Placement. Company name maps to clientCorporationName, address fields map to address fields, and website maps to url. We deduplicate on company name during import and flag any Crelate company that has no associated employer contacts or job orders for manual review before parent record sequencing continues.
Job → JobOrder
Crelate Jobs map to Bullhorn JobOrder.
How it maps
The ClientCorporation reference resolves to the migrated ClientCorporation record by name or ID match. Crelate job status (Open, Closed, Filled) maps to Bullhorn jobStatus (Open, Interview, Offer, Extended, Placed, Closed). Custom fields on Jobs migrate to JobOrder custom fields subject to the 20-field cap. We preserve the Crelate job ID in a custom field for placement chain resolution later.
Placement → Placement
Crelate Placements map to Bullhorn Placement.
How it maps
This is the last object imported because Placements require existing JobOrder, Candidate, and ClientCorporation records to satisfy foreign key constraints. We resolve the parent JobOrder by matching on the preserved Crelate job ID in the JobOrder custom field, the Candidate by matching on name and email, and the ClientCorporation by name. Placement pay rate, bill rate, fee percentage, start date, and end date migrate directly. Crelate's 15,000-record export ceiling does not typically affect Placements because volume is lower, but we check during scoping if the customer has exceptionally high placement counts requiring segmented export.
Opportunity → JobOrder or Note (scope-dependent)
Crelate Opportunities track business development activity in the CRM layer.
How it maps
Bullhorn does not have a direct Opportunity object equivalent; business development tracking in Bullhorn is handled through JobOrder pipeline stages and Placement fees. We map Crelate Opportunities to Bullhorn JobOrder records if the Opportunity represents a job to be filled, or to Note records attached to the relevant ClientCorporation if it represents a qualified lead without an active job order. The customer chooses the mapping strategy during scoping based on how they use Crelate Opportunities.
- ContactCandidate1:1
- ContactClientContact1:1
- CompanyClientCorporation1:1
- JobJobOrder1:1
- PlacementPlacementtransformed
- OpportunityJobOrder or Notetransformed
+ 10 more in the mapping below
How Crelate and Bullhorn ATS & CRM differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | Crelate | Bullhorn ATS & CRM |
|---|---|---|
| Contact model | Single unified Contact object for candidates and client contacts | Separate Candidate (job seekers) and ClientContact (employer reps) objects with distinct schemas |
| Company model | Single Companies object | ClientCorporation for employers; ClientContact is a child of ClientCorporation |
| Job model | Jobs linked to Companies with a flat pipeline stage model | JobOrder linked to ClientCorporation; candidate submissions tracked separately as JobSubmission |
| Revenue tracking | Opportunities with pipeline stages in CRM layer | Placements capture placed hires with fee, salary, pay rate, and start date; no direct Opportunity object equivalent |
| Custom field cap | 20 custom fields per entity (Contacts, Companies, Opportunities) | Up to 35 custom object instances per entity; customText1-99 fields require explicit field mapping configuration |
| Pricing model | Per-seat with transparent tiers; Activities and Forms are add-ons | Per-seat base plus tier-gated modules for 24/7 support, reporting, and automation add-ons |
| Activity tracking | Activities gated behind specific pricing tiers in Crelate | Activities available with Bullhorn's standard CRM tier; advanced reporting is a separate purchase |
| Automation | Built-in automation engine baked into platform | Bullhorn Jobs and ClientContact workflows require Bullhorn Automation Engine module purchase |
What to watch for in a Crelate to Bullhorn ATS & CRM migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
20 custom field per-entity cap forces data model decisions before migration
Crelate caps custom fields at 20 per entity.
How we handle it
Bullhorn supports up to 35 custom object instances per entity with customText, custom1-99 field sets. If your Crelate implementation uses 25 custom fields on Companies, you must decide which 20 to migrate before any data moves. We surface this during scoping and provide a ranked field inventory ranked by usage frequency and reporting dependency so the decision is explicit rather than discovered mid-migration. Fields dropped from migration are documented in the field inventory delivered to the customer's Bullhorn admin.
Placement chain requires three parent records to exist before import
Bullhorn Placement records require a valid JobOrder (via jobOrderId), Candidate (via candidateId), and ClientCorporation (via clientCorporationId).
How we handle it
Crelate Placements derive from existing Jobs and Candidates but do not enforce the same foreign key structure. We sequence Placements last in the migration, after all Jobs, Candidates, and ClientCorporations are committed to Bullhorn. We resolve parent references by matching on Crelate ID fields preserved in Bullhorn custom fields during the Job and Candidate migration phases. Migrations that attempt to import Placements before parent records exist fail with foreign key constraint violations and leave partial Placement records that require manual cleanup.
Bullhorn's API entity model differs from Crelate's unified schema
Crelate's REST API v3 uses a unified Contact object with a contactType property to distinguish candidates from employer contacts.
How we handle it
Bullhorn's API separates Candidate and ClientContact as distinct entity types with different field sets and different API endpoints (/entity/Candidate vs /entity/ClientContact). We resolve the contact type split during the extraction phase by evaluating Crelate contact properties, tags, and submission history to assign the correct Bullhorn entity type before any Bullhorn API calls. Migrations that load Crelate contacts into Bullhorn Candidate without this split analysis end up with employer contacts in the candidate pool.
Activity migration requires Bullhorn Activity module to be enabled
Crelate's Activities feature (calls, emails, meetings, tasks) is gated behind specific pricing tiers.
How we handle it
Bullhorn similarly requires its Activity module to be enabled for activity records to save correctly against Candidates, ClientContacts, and JobOrders. We verify that the destination Bullhorn subscription includes Activity module access before attempting to import engagement history. If the Activity module is not enabled, we migrate activities as Note records with an activity type prefix rather than native Task and Event records, and document the difference in the migration report.
Crelate's 15,000-record export ceiling requires segmented exports for large databases
Crelate's UI-based export caps individual operations at 15,000 records for Contacts, Companies, and Opportunities.
How we handle it
Databases exceeding this require multiple scoped export runs with date or ID-range filters. We automate segmented exports using Crelate's API with pagination cursors, merging the result set before loading into Bullhorn. We check record counts during scoping discovery and configure segmented export scripts if the 15,000-record threshold is exceeded on any object type.
How the migration runs
Discovery and source audit
We audit the source Crelate portal across plan tier, custom field inventory per entity (flagging any entity exceeding 20 fields), activity module status, active Sequences, active automations, record counts per object, and document volume.
What this step covers
We pair this with a Bullhorn destination audit: edition selection, Activity module status, existing custom field usage, and division/role configuration. The discovery output is a written migration scope document including the field prioritization matrix, contact type split strategy, and automation inventory template.
Contact type split analysis and field mapping design
We analyze every Crelate Contact record to determine whether it represents a job seeker (maps to Bullhorn Candidate) or an employer contact (maps to Bullhorn ClientContact).
What this step covers
We evaluate contact tags, job submission history, associated company type, and any explicit contact type flags in Crelate. We design the Bullhorn field mapping configuration using Bullhorn's Field Mappings tool, pre-creating customText and custom1-99 field assignments for every Crelate custom field that falls within the 20-field cap. Field mapping is deployed to a Bullhorn sandbox for validation before production migration begins.
Sandbox migration and reconciliation
We run a full migration into Bullhorn's sandbox using production-like data volume.
What this step covers
The customer's Bullhorn admin reconciles record counts (ClientCorporations in, ClientContacts in, Candidates in, JobOrders in, Placements in), spot-checks 25-50 random records against Crelate source, and validates that Placement chains correctly link to their parent JobOrder and Candidate. Field mapping corrections and any custom field cap conflicts are resolved in sandbox before production migration. Bullhorn sandbox refresh is the customer's responsibility; we schedule migration validation around refresh windows.
Owner reconciliation and User provisioning
We extract every distinct Crelate User referenced on Contacts, Companies, Jobs, and Placements and match by email against the Bullhorn destination org's User table.
What this step covers
Any Crelate User without a matching Bullhorn User goes to a reconciliation queue. The customer's Bullhorn admin provisions missing Users with appropriate roles and divisions. Migration cannot proceed past this step because Candidate, ClientContact, JobOrder, and Placement all reference an Owner field that must resolve to a valid Bullhorn User.
Production migration in dependency order
We run production migration in record-dependency order: ClientCorporations (first, as the root employer entity), Candidates and ClientContacts (in parallel, after ClientCorporation is established for the ClientContact clientCorporationId lookup), JobOrders (with clientCorporationId resolved), Activities (Tasks, Events, Notes via Bullhorn REST API), Placements (last, with jobOrderId, candidateId, and clientCorporationId resolved), Documents (ContentDocument upload and linking), Tags.
What this step covers
Each phase emits a row-count reconciliation report before the next phase begins. We handle Crelate's 120 req/min API rate limit with request batching and exponential backoff during extraction.
Cutover, validation, and automation rebuild handoff
We freeze Crelate writes during cutover, run a final delta migration of any records modified during the migration window, then enable Bullhorn as the system of record.
What this step covers
We deliver the Sequence and automation inventory document to the customer's Bullhorn admin or Bullhorn Automation Engine partner. We support a one-week hypercare window where we resolve reconciliation issues raised by the recruiting team. We do not rebuild Crelate Sequences or automations as Bullhorn workflows inside migration scope; that is a separate engagement with a Bullhorn implementation partner.
- Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
A quote scales with record volume, custom field prioritization scope, and placement chain complexity. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Crelate to Bullhorn ATS & CRM →Why teams move from Crelate to Bullhorn ATS & CRM
- Crelate's per-seat pricing layers add-on costs for Activities, Activity Forms, and Core Record Field customization that are included in Bullhorn's base CRM tier. Reviewers on G2 and Capterra cite the cumulative cost of Crelate's add-on model as a driver for switching, especially for teams that need engagement tracking beyond basic contact management. Bullhorn's base ATS+CRM includes activity logging across Candidates and ClientContacts without tier-gated restrictions, which flattens the effective per-seat cost for activity-heavy recruiting workflows.
- Bullhorn is the industry-standard ATS for staffing and recruiting agencies, with over 10,000 customers and deep integrations with job boards (Indeed, LinkedIn, Monster), VMS platforms (Bullhorn VMS/Synegen), and back-office tools (Bullhorn Back Office, Bullhorn Billing). Teams that outgrow Crelate's integration ecosystem move to Bullhorn because Bullhorn Marketplace listings represent staffing-specific connectors rather than generic Zapier-routed integrations.
- Bullhorn's relational staffing model encodes the full recruiting lifecycle in its object schema—Candidate submitted to JobOrder via JobSubmission, which converts to Placement when filled. Teams with high-volume placement tracking move from Crelate because Bullhorn's Placement object captures pay rate, bill rate, fee percentage, start date, and end-to-end submission history natively, whereas Crelate collapses this into a pipeline-stage model that loses submission-level granularity.
- Bullhorn supports up to 35 custom object instances per entity with customText, custom1, and custom2 field sets, versus Crelate's 20 custom fields per entity cap. Teams with complex data requirements for specific industries (healthcare, IT staffing, executive search) move to Bullhorn because the custom field headroom accommodates firm-specific compliance fields, certification tracking, and multi-state regulatory data without forcing field consolidation during migration.
- Crelate's customer service and billing support receive consistent negative feedback in reviews, with Reddit and G2 reviewers citing responsiveness issues and unclear billing communications. Bullhorn offers tiered support including 24/7 phone support at higher tiers, which is a meaningful differentiator for agencies that need guaranteed response times during placement crunches or billing disputes.
Questions, answered
Crelate to Bullhorn ATS & CRM migration questions
How long does a Crelate to Bullhorn migration take?
Most migrations land between two and four weeks for databases under 10,000 Contacts, 2,000 Jobs, and 500 Placements with no custom object complications. Migrations with high placement volume, complex multi-division ClientCorporation structures, or large activity histories requiring Bullhorn Activity module configuration move to six to ten weeks because of parent-record dependency sequencing, custom field prioritization discussions, and Bullhorn sandbox validation cycles.
Do Crelate Sequences and automations migrate to Bullhorn?
No. Crelate Sequences (automated outreach cadences with templated emails, tasks, and text steps) and automations (property-triggered workflow rules) are platform-native features that cannot be exported as portable artifacts. Bullhorn's Automation Engine is a separate module with a different rule-builder model. We do not migrate them as code. We deliver a written inventory of every active Crelate Sequence and automation with its trigger, conditions, actions, and a recommended Bullhorn Automation Engine equivalent or sales engagement tool integration. The customer's Bullhorn admin or a Bullhorn partner rebuilds them post-migration.
What happens to my custom fields during migration?
Crelate caps custom fields at 20 per entity. If any entity type in your Crelate database exceeds this, we work with you during scoping to rank your existing custom fields by usage frequency and reporting dependency. The top 20 migrate to Bullhorn's customText and custom1-99 field sets via Bullhorn's Field Mappings tool. Fields above the cap are documented in the field inventory delivered to your Bullhorn admin. We recommend deciding on field prioritization before migration begins so the mapping configuration is ready on day one in Bullhorn.
How do you handle Placements that depend on Jobs and Candidates that have not been imported yet?
Bullhorn Placement records require valid JobOrder, Candidate, and ClientCorporation foreign keys. We sequence Placements as the last object in the migration after all other records are committed. We preserve the original Crelate Job ID in a Bullhorn custom field during JobOrder import and use it as a lookup key when importing Placements. The parent JobOrder and Candidate must exist in Bullhorn before the Placement import phase begins; we validate this dependency chain in the reconciliation report before proceeding to Placements.
Will my candidate and employer contact records be in the right Bullhorn entity type?
Yes. Crelate's unified Contact object requires a contact type split during migration: job seekers go to Bullhorn Candidate and employer contacts go to Bullhorn ClientContact. We perform this split during the extraction phase by evaluating Crelate contact tags, job submission history, and associated company type. The split is applied before any Bullhorn API calls so that Candidate and ClientContact records land in the correct entity buckets with the correct field sets.
What about Crelate's 120 requests per minute API rate limit during extraction?
Crelate's API enforces a 120 requests per minute limit per IP. For a database of 8,000 Contacts, sequential API extraction would take over 65 minutes of pure API time, excluding network latency and error handling. We handle this by batching requests, implementing exponential backoff, and distributing extraction across off-peak migration windows to stay within the ceiling without blocking on retries. The extraction script tracks API response headers and adjusts request frequency dynamically if rate limit responses are detected.
Related migrations
Sources: official documentation
- Understanding Custom Objects — Bullhorn ATS
- Understanding Bullhorn Field Edit Types
- A guide to data hygiene for staffing firms — Bullhorn
- How to Import Data into Bullhorn — Bullhorn ATS
- Import Data+ — Crelate, Inc. Help Center
- What is an ATS Data Migration? — Crelate
- Crelate Professional Services — Customer Success
Get a quote
Moving from Crelate to Bullhorn ATS & CRM?
Tell us roughly how many records and objects you have. We scope the mapping and the Bullhorn ATS & CRM setup with you, then send a quote.
Get a quote