Migrate from Aperio to Crelate

Aperio employee records map directly to Crelate Contacts. We extract name fields, title, department, manager relationship, and hire date from the CSV export and load them into the corresponding Crelate Contact fields. The manager relationship resolves as a Contact lookup by email. Employee IDs are preserved in a custom field aperio_employee_id__c for reconciliation. Resume or profile attachments attach via ContentDocumentLink to the Contact record after import.

Aperio goals lack a native Crelate equivalent. We map the goal title, description, status, and target date to Crelate Contact custom fields (up to the 20-field limit). Goal content that exceeds the field cap migrates as a Crelate Tag on the Contact. We extract goal_id and parent_goal_id pairs from the CSV to identify orphaned or circular references before loading, and flag any unreconciled goals for the customer admin.

Aperio goal hierarchies flatten to parent_goal_id in the CSV export. We reconstruct the hierarchy by grouping goals by parent_goal_id and tagging child goals on the parent Contact as a related tag with a goal_rank prefix (e.g., 'G1_child_1', 'G1_child_2') so the relationship is recoverable in Crelate without native hierarchy support.

Aperio performance reviews are cycle-based records with ratings, reviewer comments, and competency scores. We map review date, overall rating, and status to Cperio Contact custom fields. Detailed competency ratings and free-text comments exceed Crelate's 20-field limit on Contacts; we store these as Crelate Activity Forms linked to the Contact with a custom activity type 'Performance Review' and field mappings copying responses to Contact columns. Review cycles are preserved as Tags on the Contact (e.g., 'Review_2024_Q4').

Aperio review templates define competency sections, rating scales, and mandatory fields. Crelate has no native review template object, but activity forms with field mappings provide a structural equivalent. We export template definitions and deliver a written field map documenting each Aperio competency and rating scale with its recommended Crelate Activity Form question and Contact field pairing. The customer's admin builds the form in Crelate from this reference.

Aperio competency libraries are referenced within reviews and templates. Crelate has no native competency library. We export competency definitions and their rating scales and deliver a written competency reference document mapped to the Activity Form questions and field mappings where they should land in Crelate. The customer's admin rebuilds the competency library as part of their activity form setup.

Aperio development plans track growth actions tied to employees and review outcomes. Crelate has no development plan object. We extract plan records with milestones and timelines from the CSV and map plan titles and key milestones to Crelate Contact tags. Detailed plan content migrates as a Note on the Contact with the plan body preserved in rich text. Goal links are handled through the goal mapping described above.

Aperio departments represent the organizational hierarchy with parent-child relationships. Crelate's org model is company-based rather than department-based. We map each Aperio department to a Crelate Contact tag (e.g., 'Dept_Engineering', 'Dept_Sales') and optionally to a Crelate Company record if the customer wants to represent internal cost centers as Company entities. The department hierarchy does not have a direct Crelate equivalent; we document the hierarchy as a reference structure for the customer admin.

Aperio job titles are associated with employees and used as criteria within review templates. Crelate has no native job title library. We export the full job title roster and map titles to a custom field job_title__c on the Contact record. Titles that appear in multiple Aperio contexts (review criteria, competency weighting) are noted in the job title reference document delivered alongside the migration.

Aperio review cycles are temporal containers that batch related reviews with start and end dates. Crelate has no cycle object. We extract cycle metadata and apply a tag to each Contact that participated in the cycle (e.g., 'Cycle_2024_H1'). Cycle dates and status are preserved in a custom field last_review_cycle__c on the Contact for reporting purposes.

Aperio supports custom fields on Reviews, Goals, and Development Plans with picklist and multi-select values. We identify all active custom fields during discovery, export their value sets, and map them to Crelate Contact custom fields by type. Fields that exceed Crelate's 20-field limit per entity are mapped to Crelate Tags. Where Aperio picklist values differ from any Crelate target field, we flag the discrepancy for customer resolution before loading.

Aperio owner assignments on reviews, goals, and plans reference manager or HR admin users. We extract distinct owner IDs from the CSV and match by email against the Crelate destination User table. Owners without a matching Crelate User are held in a reconciliation queue for the customer's admin to provision before record import completes.