Migrate from SmartRecruiters to Crelate

SmartRecruiters Posting records (UUID, refNumber, location, department, function, experienceLevel, typeOfEmployment) map directly to Crelate Job records. The SmartRecruiters location object (city, region, country) maps to Crelate's job location fields. Department and function map to Crelate's category and classification fields. Active job statuses from SmartRecruiters (OPEN, ON_HOLD, CLOSED, DRAFT) map to Crelate's job status values. We preserve the SmartRecruiters job reference number in a custom field for cross-system reconciliation.

SmartRecruiters Candidate records (firstName, lastName, email, phone, location, social profiles, tags) map to Crelate Person records. The Person record in Crelate serves as the core contact entity across ATS and CRM functions. We resolve duplicate detection using email as the primary key, with phone and LinkedIn URL as secondary dedupe signals. Candidate tags from SmartRecruiters migrate to Crelate Tags on the Person record.

SmartRecruiters Application records (linking Candidate to Posting with pipeline stage, source, and screening answers) map to Crelate Application records. Pipeline stage names from SmartRecruiters require mapping to Crelate's workflow stages, which are configurable per job. SmartRecruiters application source (LinkedIn, Indeed, direct, referral) maps to Crelate's application source field. Note that SmartRecruiters POST /postings/:uuid/candidates only creates applications in New status via public endpoint; any downstream stage assignments are updated in a second API call, and we sequence this correctly during migration to avoid candidates appearing at the top of the pipeline.

SmartRecruiters custom fields are entirely organization-scoped and use a fieldId/valueId/valueLabel structure fetched via the /configuration endpoint. We run a mandatory pre-migration discovery pass to enumerate every custom field and its permitted values before mapping begins. Each custom field maps to a corresponding Crelate custom field on the Person or Job record. Field types (text, date, number, picklist) are mapped to Crelate's field type equivalents. Custom field values that do not have a matching Crelate field definition are flagged for the customer's admin to configure before migration runs. Skipping this step leads to silent value loss.

SmartRecruiters User records (recruiters, hiring managers, admins) map to Crelate User records by email match. User roles and permissions from SmartRecruiters (recruiter, hiring_manager, admin, viewer) map to Crelate's role structure under Settings | Advanced Settings | User Roles. API access for SmartRecruiters OAuth 1.0 and Crelate API-key authentication are both configured during migration scoping. Any SmartRecruiters User without a matching Crelate User goes to a reconciliation queue for the customer's admin to provision.

SmartRecruiters Department records (id, label, description) map to Crelate Job Categories. The department hierarchy is preserved so job postings land in the correct organizational grouping in Crelate. Departments are referenced by ID on SmartRecruiters Job Postings, and we resolve the label during import so that the Crelate category is populated from the start rather than requiring post-migration cleanup.

SmartRecruiters Hiring Teams assigned per job (user IDs with roles) map to Crelate's job assignment structure. The recruiter assignment, hiring manager assignment, and interview panel from SmartRecruiters map to corresponding assignment records in Crelate's People module. Role-based visibility is preserved so the correct recruiters and hiring managers retain visibility over migrated jobs and candidates.

SmartRecruiters Scorecards (structured evaluation data embedded within candidate/evaluation records) map to Crelate Activity records of type evaluation or rating. The evaluator name, score, and written feedback from each SmartRecruiters scorecard section migrate to a structured Crelate activity entry linked to the Person and Job. When Crelate's native evaluation form feature is available on the customer's plan, we configure it to match the SmartRecruiters scorecard structure.

SmartRecruiters Interview records (scheduling information, interviewer assignments, outcome notes, date/time, disposition) map to Crelate Activity records. Interview date, duration, interviewer name, and outcome status migrate to the corresponding Crelate activity fields. Interview type (phone screen, video, on-site, panel) maps to a Crelate activity subtype or tag. When the destination Crelate plan includes interview scheduling integrations, we note the current scheduling tool for potential reconfiguration.

SmartRecruiters Offer records (compensation details, status, candidate linkage) migrate to Crelate Placement records with offer details in the placement notes or custom fields. Offer status (extended, accepted, declined, withdrawn) maps to Crelate's placement status workflow. Compensation fields (base salary, bonus, equity) migrate to Crelate's compensation fields if configured, or to custom fields on the Placement record.

Candidate attachments (resumes, cover letters, portfolio files) stored against SmartRecruiters Candidate profiles migrate to Crelate Documents linked to the Person record. We preserve the original filename and MIME type. File content is downloaded from SmartRecruiters via the attachment endpoint and re-uploaded to Crelate via the document upload API, linked to the correct Person ID. The SmartRecruiters attachment type (resume, cover_letter, portfolio, other) maps to Crelate's document type classification.

SmartRecruiters Assessments ordered via the /packages endpoint through third-party Marketplace integrations migrate as Crelate Activity records noting the assessment name, provider, status, and result URL if available. Assessment package and order records are integration-specific and may require reconfiguration in Crelate's Business Plus or Enterprise plan if the customer uses a similar assessment vendor. We document the current assessment provider and recommend a Crelate Marketplace alternative or re-integration step post-migration.