Migrate from Loxo to Recruit CRM & ATS

Loxo Candidates map to Recruit CRM People records. During extraction we distinguish candidate-type people from client-contact-type people using the record's associated Job and Deal associations, then set the role type on the Recruit CRM People record accordingly. We preserve all standard fields (name, email, phone, address, tags, skills) plus Loxo custom properties as custom fields on the People record.

Loxo client Contacts map to Recruit CRM People records with role type set to Client Contact. We preserve company association, custom fields, and activity history linked to the contact. Company-level lookup resolves against the Organizations imported from Loxo Client Companies.

Loxo Client Companies map directly to Recruit CRM Organizations. We preserve billing information, address, industry, and any custom fields. Parent-child hierarchy maps to Recruit CRM's organizational hierarchy if the customer has configured parent/child company structures in Loxo.

Loxo Jobs map to Recruit CRM Positions with job title, description, requirements, status, assigned team members, and custom fields preserved. Positions are imported before Candidates so that the candidate-to-position association can be resolved during the People import phase.

Loxo Deals map to Recruit CRM Deals (or Opportunities depending on the customer's CRM configuration preference). We extract the current stage name from each Deal record and apply it to the destination stage list that we configure in Recruit CRM before migration. Closed-Lost and Closed-Won status and any custom deal properties migrate as custom fields.

Loxo's per-organization customizable pipeline stages are extracted from the API and mapped to Recruit CRM stage values. We apply a customer-confirmed mapping document during import so that the stage name on each Deal matches a valid stage in Recruit CRM. Stage probability percentages migrate as metadata rather than as record values.

Loxo Placements record placed candidates against a Job and Deal with start date, compensation, and status. Recruit CRM does not have a dedicated Placement object at all tiers. We store placement data as a structured custom field set on the relevant Position or Deal record, preserving candidate reference, start date, compensation, and status so the placement history is visible in context.

Loxo custom fields on Candidates, Contacts, Jobs, and Deals are exported with field name, type, and picklist options. We create matching custom fields in Recruit CRM before migration, handling type mapping (text to text, date to date, picklist to picklist) and applying field-level mapping during import. Recruit CRM plan tier limits apply: base plan allows 15 custom fields, so we flag overflow and work with the customer to prioritize the most business-critical fields if needed.

Loxo engagement records (emails, calls, SMS, notes) migrate as activity records linked to the corresponding Recruit CRM People record. We preserve the most recent 12-24 months of activity history as recommended by Loxo's own guidance on Loxo Connect email alignment. Emails, calls, and texts attach as notes or activity entries with timestamp, direction, and content preserved. Older activity history is excluded from migration scope to reduce import volume and avoid fragmented email threads.

Binary attachments (resumes, cover letters, client agreements) are downloaded from Loxo via the API using file URL references and re-uploaded to Recruit CRM as documents linked to the parent People or Position record. Large file counts may require extended migration windows and are validated post-upload to confirm link integrity.

Loxo Owner assignments map to Recruit CRM Users by email match. We extract every distinct owner across all record types, match by email against the destination system's user table, and flag any owners without a corresponding Recruit CRM user for the customer's admin to provision before record import resumes.

Loxo Outreach sequences, cadence rules, and automation triggers are not exposed via the public API and cannot be migrated as active automation. We preserve the most recent outreach enrollment status, step position, and campaign name as custom fields on the Candidate record in Recruit CRM so the destination team knows where each candidate sits in a cadence without needing to rebuild from scratch. Active sequences require rebuild in Recruit CRM's native automation builder.