Migrate from Loxo to Crelate

Loxo Candidates map to Crelate's Person as the core individual record and Contact as the recruiting-specific record with submission history and pipeline stage. Because Loxo creates a separate Candidate profile for the same person when they apply to multiple Jobs, we deduplicate at migration time: matching on email address and name produces one Crelate Person with linked Contact records per original Job assignment. We flag the deduplication decision for customer approval before finalizing. Tags, skills, and custom properties migrate to the Contact record in Crelate.

Loxo Client Companies map directly to Crelate Companies. We preserve billing address, industry classification, and the parent-child hierarchy if the Loxo instance uses parent company assignments. The Company record is created before Person and Contact imports so that the company lookup is satisfied at insert time.

Loxo Jobs map to Crelate Job Orders with full description, requirements, assigned team members, and custom fields. We preserve the job status (open, filled, cancelled) and any pipeline stage association. Crelate's job portal and application form links are documented separately for portal reconfiguration by the customer admin.

Loxo Deals map to Crelate Opportunities with deal value, stage name, and owner preserved. Stage names migrate as-is for single-pipeline Loxo instances. For multi-pipeline Loxo accounts, we collapse pipeline names into Opportunity custom fields and map all deals to Crelate's single pipeline with a customer-confirmed stage name mapping. Loxo's customizable pipeline stages per org are extracted and applied against Crelate's stage list.

Loxo Placements (placed candidates against a Job and Deal) map to a Contact custom property in Crelate because Crelate does not have a dedicated Placement object equivalent to Loxo's. We store placement status, start date, compensation details, and the related Job and Company as Contact properties, preserving the full placement history as a searchable record for the customer's back-office.

Loxo activity records (emails, calls, texts) migrate as Crelate Activity records linked to the Person or Contact. Call duration, disposition, and recording URL transfer to custom activity fields. We scope activity history to the most recent 12-24 months to reduce the risk of importing fragmented Loxo Connect email threads, and we validate email-address ownership before mapping the sender-recipient relationship. SMS logs migrate as activity records with message content preserved.

All tag associations on Candidates, Contacts, Jobs, and Deals export from Loxo and apply in Crelate. Tags not already present in Crelate are created at migration time. We preserve the tag-to-record relationship per object so that tag-based reporting and filters work immediately after cutover.

Loxo custom fields on Candidates, Contacts, Jobs, and Deals are extracted with field name, data type, and option lists for documentation. Crelate's custom field system uses a custom forms builder with field mapping rules per object (Contacts, Companies, Opportunities). We deliver a written schema map that the customer admin uses to configure each custom field in Crelate's custom form builder; the field mapping rules from Crelate's documentation are included in this deliverable.

Binary attachments (resumes, cover letters, client agreements) are extracted from Loxo as file URLs via API, downloaded to our migration staging environment, and re-uploaded to Crelate's file management linked to the corresponding Person, Contact, Job Order, or Company record. Large file counts (over 5,000 attachments) may require extended staging time for download and re-upload validation.

Loxo owner assignments on all records map to Crelate Users resolved by email match. Any Loxo Owner without a matching Crelate User is held in a reconciliation queue. The customer admin provisions missing Crelate Users before record import resumes, because OwnerId references are required on most standard object imports.

Loxo Outreach sequences, email cadence rules, SMS steps, and auto follow-up triggers are not exposed through the public API and cannot be migrated as code. We extract campaign enrollment history and the most recent outreach status per Candidate as custom Contact properties, so the destination team knows where each candidate sits in a sequence. A written campaign inventory with step order, delay rules, and trigger logic is delivered to the customer for manual rebuild in Crelate's configuration.

Loxo workflows built with the automation builder are not accessible via API for export and cannot be migrated to Crelate, which uses a different automation model. We deliver a written inventory of every active workflow with trigger conditions, action steps, and recommended Crelate equivalents, so the customer's admin can rebuild after cutover.

Loxo's client-facing portal configuration, including branding, shared job visibility settings, and report templates, is tied to instance-level portal setup and is not accessible via API. Crelate's client portal configuration is built separately in Crelate's portal settings. We document the current Loxo portal configuration for the customer to reference during Crelate portal setup, but the settings themselves require manual rebuild.

Loxo Source candidate enrichment data and AI matching scores are proprietary to Loxo's platform and not exportable via API. We do not migrate Loxo Source profiles or sourcing match scores. The customer's admin should evaluate Crelate's Discover Agent (conversational search) or an external enrichment provider as a replacement for sourcing intelligence after migration.

Loxo pipeline stages are customizable per organization. We extract the full stage list from Loxo's API and produce a customer-confirmed mapping to Crelate's Opportunity stage names. Probability percentages migrate from Loxo to Crelate's stage weight fields. If Loxo uses multiple pipelines, all stage names map into the single Crelate pipeline with pipeline-of-origin stored as a custom field.