Migrate from Smart Recruit Online to Recruit CRM & ATS

Smart Recruit Online Candidate records map directly to Recruit CRM Candidates. We preserve candidate ID as a source reference field, migrate core fields (name, email, phone, location, source), and resolve custom fields using the SmartOS fieldId/valueId/valueLabel schema mapped to Recruit CRM custom fields during the pre-migration audit. Resume files export as document attachments with metadata preserved; file URLs are re-hosted since source storage is Smart Recruit Online-controlled.

Smart Recruit Online Job records map to Recruit CRM Jobs. We migrate job title, reference number, location, department, function, employment type, experience level, and job description. The Smart Recruit Online job status (Draft, Open, On Hold, Closed) maps to Recruit CRM job status values. Department and function reference data migrate as structured fields to preserve organizational context.

Smart Recruit Online Application records (linking a Candidate to a Job with a current status) map to Recruit CRM candidate records on a job, with the application status reflected in the job's candidate stage. Application timestamps (applied date, last modified) and assigned Hirer migrate as activity metadata. Status history is preserved as a stage-change log in Recruit CRM's candidate timeline.

Smart Recruit Online Hirer records (internal users who create or own Jobs and Applications) map to Recruit CRM Users by email match. Hirers without a matching Recruit CRM User are held in a reconciliation queue for the customer to provision accounts before record import. User-level permissions (recruiter, admin, hiring manager) are mapped to Recruit CRM role equivalents during scoping.

Smart Recruit Online Postings (job advertisements linked to Jobs with job board distribution records) map to Recruit CRM Job records with a distribution checklist delivered as a separate handoff document. The posting name, reference number, released date, and location data including remote-work flags migrate. Job board distribution to Indeed, LinkedIn, and other boards is a Smart Recruit Online-controlled action and requires manual reposting in Recruit CRM.

Smart Recruit Online configurable pipeline stages within Jobs (stage name, order, and associated automations) map to Recruit CRM job stage configurations. We extract the current stage definitions during the pre-migration audit, map stage names and probabilities to equivalent Recruit CRM stage values, and deliver the stage configuration as a structured setup guide. Stage-triggered automations are documented and not migrated as automation rules.

Smart Recruit Online CustomField objects use a fieldId/valueId/valueLabel structure that is tenant-defined, routinely including 15-30+ fields with non-standard labels on Candidate and Job records. We capture the full custom field schema during scoping, map value labels to Recruit CRM custom field options, and validate picklist continuity for multi-select fields. Missing or mismatched custom fields are flagged before the migration run begins to avoid silent data loss.

Smart Recruit Online workflow rules, approval chains, and stage-triggered actions are configuration objects in the SmartOS platform layer, not data records. We do not migrate them as data. We export active workflow definitions as a written automation audit inventory with trigger conditions, action sequences, and recommended Recruit CRM equivalents. The customer's admin rebuilds these post-migration.

Offer management is available on Smart Recruit Online higher tiers. We migrate offer status and key details where exposed via API as notes or custom fields on the candidate record. Offer templates and approval workflows require manual setup in Recruit CRM as part of the post-migration configuration phase.

Candidate email threads accessible via the Smart Recruit Online candidate detail endpoint migrate as activity notes on Recruit CRM candidate records. Thread integrity is preserved only for emails sent through Smart Recruit Online natively; external email imports may not carry full thread context. Email attachments migrate as candidate document attachments with metadata preserved.