Migrate from Smart Recruit Online to Crelate

Smart Recruit Online Candidate records map to Crelate Person records with a 1:1 ID mapping. The candidate's name, email, phone, location, and source attribution transfer directly. Smart Recruit Online's CustomField arrays (fieldId/valueId/valueLabel) map to Crelate custom fields on the Person object by matching the field label. Candidates without a matching Crelate organization are held in a staging queue until the organization mapping is confirmed.

Smart Recruit Online Job records map to Crelate Job records with the job title, description, location, department, employment type, and experience level preserved. The Smart Recruit Online job reference number becomes a custom field on the Crelate Job. Jobs with multiple Postings are consolidated into a single Crelate Job; the individual posting distribution records are documented separately as they do not carry over to Crelate.

Smart Recruit Online Application records linking a Candidate to a Job map to Crelate Job Submission records. The application status history transfers as a series of stage-change entries in the Job Submission activity log. Smart Recruit Online stage names are mapped to the Crelate pipeline stages designated during scoping. The assigned Hirer from Smart Recruit Online maps to the Crelate user who will own the Job Submission.

Smart Recruit Online pipeline stages are configurable per Job and include stage order, probability, and any stage-triggered automations. Crelate pipeline stages are global objects referenced by Jobs. We extract every distinct stage definition from Smart Recruit Online during the pre-migration audit, present the customer with a stage-to-stage mapping worksheet, and configure the corresponding Crelate pipeline stages before any Job Submission records are imported. Automation triggers on stages are documented for manual rebuild.

Smart Recruit Online CustomField objects use a fieldId/valueId/valueLabel schema that is entirely tenant-defined. We capture the full custom field schema during scoping, build a mapping table against Crelate's custom field definitions (set up per object in Crelate Settings > Custom Forms), and validate picklist value continuity for multi-select fields. Crelate's custom field naming and data types are configured before the migration run. Any custom fields without an equivalent in Crelate are flagged in the migration scope document.

Smart Recruit Online Hirer records (internal users who own Jobs and Applications) map to Crelate User records. We resolve Hirers by email address match against the Crelate destination account's user list. Hirers without a matching Crelate User are held in a reconciliation queue for the customer's admin to provision before Job Submission import begins. Inactive Smart Recruit Online Hirers are optionally mapped to inactive Crelate Users to preserve historical assignment records.

Smart Recruit Online stores Department and Function as structured fields on Job objects with id and label. Crelate does not have a native department hierarchy; we map these to Crelate Tags (for flat taxonomy) or a custom picklist field on the Job object depending on the customer's preference confirmed during scoping.

Resume files and attachments associated with Smart Recruit Online Candidates and Applications are exported from Smart Recruit Online storage, re-hosted in Crelate's document storage, and linked to the corresponding Crelate Person or Job Submission record. File URLs in Smart Recruit Online are not transferable because the source storage is Smart Recruit Online-controlled. We preserve file name, MIME type, upload date, and the Smart Recruit Online record reference as metadata on the Crelate attachment.

Candidate email threads accessible via the Smart Recruit Online candidate detail endpoint migrate to Crelate Activity records with type = Email. Thread integrity depends on the emails having been sent through Smart Recruit Online natively; external email imports may not carry a complete thread history. We preserve the email body, timestamp, and sender-recipient relationship as activity details. Email campaigns (bulk outbound) are not migrated as Crelate does not have a native bulk campaign feature in the same model.

Smart Recruit Online call engagements (type = CALL) map to Crelate Activity records with type = Call. Call duration, disposition, and recording URL transfer to custom Activity fields. The original Smart Recruit Online timestamp becomes the Crelate Activity date for timeline ordering.

Smart Recruit Online meeting engagements map to Crelate Activity records with type = Meeting. Start time, end time, location, and attendees transfer. Attendee mapping in Crelate links to the corresponding Person records via the activity's participant records.

Smart Recruit Online Note engagements migrate to Crelate Activity records with type = Note. The note body transfers as the activity details. Notes linked to specific Smart Recruit Online records (Candidate, Application, Job) are linked to the corresponding Crelate records via the parent-record lookup resolved at migration time.

Smart Recruit Online Task engagements map to Crelate Activity records with type = To-Do. Task status, due date, and assignment transfer, with the Smart Recruit Online Hirer mapped to the corresponding Crelate User via the owner reconciliation step.