Migrate your Loxo data

Candidates is Loxo's primary people object, holding resume, skills, experience, tags, and communication history. We export all standard candidate fields and custom properties via the API. Duplicate detection during import into the destination is recommended as Loxo creates separate profiles for the same person across different Jobs.

Loxo stores client contacts and candidate contacts as distinct records with phone, email, company association, and custom fields. We map these to the destination CRM's Contact or Person object, preserving ownership assignments and lifecycle stages.

Jobs in Loxo represent open requisitions linked to pipeline stages, descriptions, requirements, and assigned team members. We preserve the full job record including custom fields and its pipeline association.

Deals track client assignments and revenue in Loxo's CRM. Pipeline stages vary by org because users can customize them. We map Deal records and stage names to the destination CRM's Opportunities or Deals, applying a customer-confirmed stage mapping at import time.

Placements record placed candidates against a Job and Deal, including start date, compensation, and status. Not all destination CRMs have a dedicated Placement object; where absent, we store placement data as custom fields on the Deal or a linked Contact record.

Client Companies in Loxo hold billing info, contacts, and associated Deals and Placements. We export and map these to the destination's Account or Organization object, preserving hierarchy if parent/child companies exist.

Pipeline stages are customizable per Loxo org. The current stage names are stored on the Deal record. We extract the full stage list from the API and apply a customer-confirmed mapping to the destination pipeline at migration time.

Loxo supports custom fields on Candidates, Contacts, Jobs, and Deals. Custom field schemas vary by org. We extract the field name, type, and options for each object and apply a field-level mapping during the load into the destination platform.

Loxo logs all communication threads — emails, calls, and SMS — against Candidates and Contacts. These are stored as threaded activity records. We preserve the most recent N months of activity history as agreed in the scoping call; very large activity volumes may require pagination-aware extraction to stay within API limits.

Candidates, Contacts, and Jobs can be tagged with custom labels. We export all tag associations and apply them at the destination, creating the tag in the target system if it does not already exist.

Binary attachments — resumes, cover letters, client agreements — are stored per record. We extract file URLs from the API and download them for re-upload to the destination. Large file counts may require chunked processing.

Every record in Loxo has an assigned Owner. Owner IDs map to user emails. We map Loxo owner assignments to the corresponding user in the destination system, creating placeholder assignments for any owner without a destination match.

Loxo Outreach manages automated email and SMS sequences with cadence rules and tracking. Campaign configuration — templates, steps, and trigger logic — is not fully exposed via the public API. We do not migrate active campaign automation; instead we preserve campaign member statuses as Candidate custom properties so outreach history is not lost.

The client-facing portal configuration — branding, shared job visibility, report templates — is tied to the instance-level portal setup and is not accessible via API. These settings must be reconfigured manually in the destination platform post-migration.