Migrate from Longlist to Recruit CRM & ATS

Longlist candidate records map to Recruit CRM Candidate. The Longlist candidate name, email address, and phone number transfer to the standard Candidate fields. Any LinkedIn URL from Longlist enrichment maps to a custom URL field or the Candidate's social profile field. Enrichment metadata (data confidence score, last refreshed date, enrichment source domain) migrates to custom Candidate fields we pre-create in Recruit CRM before import. The Longlist export file uses UTF-8 encoding; we validate character encoding before import to prevent accented names and international phone formats from corrupting.

Email and phone number migrate from Longlist directly to Recruit CRM Candidate's standard email and phone fields. Longlist sometimes surfaces multiple email addresses or phone numbers for a single candidate; we map the primary (highest-confidence) email to the standard field and write secondary addresses to a custom multi-value text field so that no enrichment data is dropped during import.

Longlist list groups (named collections of candidates that sourcers created during research) map to Recruit CRM Tags. During scoping, the customer defines whether lists should become tag values on the Candidate record or a separate Tag object with a TopicAssignment-style association. Free-form tags applied by sourcers also map to Tags. We deliver the complete tag taxonomy from Longlist as a structured CSV so the customer's Recruit CRM admin can configure the Tags object before import.

Longlist records the domain or tool where enrichment occurred (LinkedIn profile URL, job board page URL, sourcing tool). We map this to a custom Candidate field (source_url__c) and, where Longlist provides a structured source type, to the Candidate Source picklist. This preserves the research provenance that sourcers rely on for channel attribution and helps Recruit CRM users understand where each contact originated without leaving the candidate profile.

Free-form tags applied by sourcers inside Longlist migrate to Recruit CRM Tags on the Candidate record. Tags with consistent naming conventions across the export map cleanly. Tags that are free text with typos, inconsistent casing, or duplicates are flagged in the data audit report for the customer's admin to canonicalize before import.

Longlist enriches records with metadata that has no native equivalent in Recruit CRM's standard Candidate schema — data confidence score, enrichment timestamp, verification method, and secondary email or phone. We pre-create these as custom fields in Recruit CRM before migration using the API field names from the Longlist export. The customer's admin names the custom fields during scoping so the labels are meaningful to recruiters who will use them in day-to-day filtering.

Longlist records the sourcer who created or last modified a candidate profile. We match by email address against Recruit CRM User records. Any Longlist owner without a matching Recruit CRM User is held in a reconciliation queue for the admin to provision before candidate import begins. Owner is assigned after candidate insert so that the OwnerId reference is satisfied at migration time.

Longlist has no job order or vacancy records — sourced candidates are not tied to open roles within the tool. We do not migrate any job data because none exists in Longlist. The customer's Recruit CRM admin creates Job records post-migration and associates migrated candidates manually or through Recruit CRM's candidate matching feature. We document this as a post-migration step in the handoff summary.

Longlist has no client or company relationship records — it focuses exclusively on candidate contact enrichment. We do not migrate any client data because none exists in Longlist. The customer's Recruit CRM admin creates Client records post-migration and associates migrated candidates to client jobs as the recruiting pipeline develops.

Longlist does not expose workflows, sequences, or automations via its data export layer. There are no automation records to migrate. We deliver a written note confirming zero automation scope so that the customer understands the migration is data-only and that any candidate nurture sequences or task automations must be created fresh in Recruit CRM post-migration.