Migrate from Aperio to Recruit CRM & ATS

Aperio employee records map to Recruit CRM Candidate records. We map standard fields (first_name, last_name, email, phone, department, job_title, hire_date, manager) directly into the Candidate object. The Candidate status defaults to a value representing that these are internal employees being onboarded into the recruiting workflow (Client decides whether to treat them as Candidates, Contacts, or both). Employee ID is preserved as a custom field for audit and reference. Aperio employees who are also active recruiters in the system map to Recruit CRM Users with the appropriate recruiter role.

Aperio department records map to Recruit CRM organizational structures. Recruit CRM does not have a native Department object, so we map departments to a combination of the candidate's department field and a custom lookup or tag structure depending on the Recruit CRM edition in use. We document the chosen structure during scoping and flag whether the customer needs a custom field added for organizational hierarchy.

Aperio job titles map to the job_title custom field on the Candidate object in Recruit CRM. We export the full job title roster during discovery and ensure all active titles appear in the candidate record. If job titles are used as criteria within Aperio review templates, we note this relationship for the customer's HR team as the review template workflow does not migrate.

Aperio Performance Reviews have no direct equivalent object in Recruit CRM. Recruit CRM's candidate notes are free-text, unstructured records. We export review summaries as formatted Note records attached to the corresponding Candidate in Recruit CRM, preserving the review cycle name, overall rating, and reviewer comments. The structured rating breakdown against competencies does not carry over in typed form. We deliver a written schema inventory of all Performance Review fields that the customer's HR and IT teams can use to assess a dedicated performance management tool post-migration.

Aperio goal records (including parent-child hierarchy via parent_goal_id) do not have a Recruit CRM equivalent. Standalone goals migrate as Note records attached to the Candidate with the goal title, description, and status. Child goals reference their parent via text notation in the Note body. We flag circular references and orphaned child goals detected during the flattening phase. Recruit CRM Tasks are activity-level and not suited to hierarchical goal tracking. Customers needing goal management post-migration should plan for a dedicated tool.

Development plans with milestones and timelines migrate as Note records attached to the Candidate. We extract plan title, description, associated milestones, and target dates, formatting them as structured text within the Note. The milestone-to-timeline relationship is not preserved as a typed object relationship in Recruit CRM. We flag this limitation in the migration handoff documentation so the customer's HR team can decide whether to replicate the plan structure in a dedicated development or LMS tool.

Aperio competency library records (competency definitions with rating scales) do not have a Recruit CRM equivalent object. We export competency names and map them to the Skills field on the Candidate record in Recruit CRM where the skill is relevant to recruiting or placement. For competencies that represent internal HR assessment criteria with no recruiting analog, we deliver them as a structured data inventory document.

Aperio Review Cycles (temporal containers with start/end dates and associated templates) have no equivalent in Recruit CRM. Cycle metadata migrates as a custom text field on the Candidate record indicating the last review cycle attended and its status. We flag this for the customer's HR team because annual or semi-annual review cadence tracking is an HR operations requirement that Recruit CRM does not fulfill.

Review templates define the structure of Aperio reviews including competency sections, rating scales, and mandatory fields. Recruit CRM has no template object for performance reviews. We do not migrate review templates as code or configuration. We deliver a written inventory of every active template with its sections, rating scale, and conditional logic so the customer's HR admin can evaluate alternatives.

Aperio custom fields on Reviews, Goals, and Development Plans require manual identification during scoping because they do not self-document in CSV exports. We identify all active custom fields, export sample values, and map them to Recruit CRM custom fields by type (text, number, picklist, date). Value sets are reconciled against Recruit CRM picklist options. Custom fields that cannot map (complex types, multi-select with no Recruit CRM equivalent) are flagged for customer resolution before the load phase.