Migrate from Sympa to Crelate

Sympa Employee records map to Crelate People as the core Contact record. First name, last name, email, phone, job title, department, start date, and employment status migrate to their Crelate equivalents. Active status maps to Crelate's candidate status or a custom active-terminated field. Employment type (full-time, part-time, contractor) maps to a custom field if no default Crelate field applies. We resolve the source Employee ID as a custom field for cross-reference.

Sympa org units and reporting hierarchies do not map to Crelate's native Company object because Crelate Companies represent client organizations, not internal departments. We map the top-level org unit as a Company record for reference, and preserve the full parent-child hierarchy in a custom org_chart__c field (JSON or delimited) for the customer to reconstruct in Crelate's org structure or a linked HRIS. Sub-departments do not have a native Crelate equivalent and are flagged for manual rebuild.

Sympa's effective-dated compensation entries (salary, bonus, equity grants) have no native Crelate object. We map the most recent salary to a custom monetary field on the Person record, and preserve the full compensation timeline in a custom salary_history__c field (JSON) for audit or reconfiguration in a supplemental HRIS. Customers typically pair this migration with Rippling, Gusto, or BambooHR for payroll and compensation management post-migration.

Sympa's accrued time-off and leave entitlement balances do not migrate to Crelate. Crelate has no time-off object and no PTO tracking capability. We export current balances as a CSV reference file for the customer's new HRIS admin to reconfigure accrual rules and entitlement values. The export includes employee name, leave type, accrued balance, used balance, and remaining balance per Sympa's snapshot.

Sympa stores job title changes, department transfers, and manager updates as effective-dated events per Employee. We preserve the chronological sequence of employment events in a custom job_history__c field on the Person record as JSON, including effective date, old title, new title, old department, new department, and old manager. The customer can parse this for reporting or migrate it to a dedicated HRIS with an employment history object.

Sympa documents attached to Employee records (contracts, certifications, compliance records) migrate to Crelate ContentDocument records linked via ContentDocumentLink to the Person record. We preserve the original filename, file type, upload date, and attached-by user where available. Documents larger than the Crelate storage limit are flagged for the customer's admin to decide whether to archive externally or reduce resolution before import.

Sympa Users (system login accounts) do not map 1:1 to Crelate Users because Sympa roles (HR Admin, Manager, Employee Self-Service) differ from Crelate roles (Recruiter, Sales, Admin). We extract the email, name, and active status of Sympa users and provide a Crelate user provisioning list grouped by recommended role assignment. The customer's Crelate admin provisions users and permissions during the cutover window.

Sympa custom fields on Employee records require a pre-migration tenant audit because field names, data types, and picklist values vary per instance. We cross-reference each Sympa custom field against Crelate's available field types (Short/Long Answer, Date, Numeric, Picklist, Multi-select, Monetary, Boolean) and create matching Crelate custom fields before migration. Any Sympa custom field without a Crelate equivalent is mapped to the closest type with a transformation documented in the field mapping reference.

Sympa's active/terminated/on-leave status maps to a custom picklist field on Crelate Person. Terminated employees migrate with their termination date preserved. Active employees are set to the Crelate default status. We flag any Sympa status value that does not map directly to a Crelate status and document the transformation for the customer's review before migration.

If the Sympa instance was used for job requisitions or candidate tracking in addition to HR, those records map to Crelate Opportunity (Job Order) with pipeline stages mapped to Crelate's Opportunity stages. Submissions map to Crelate's submission tracking linked to the Opportunity and the Person. This mapping applies only when Sympa's recruiting module was in active use; we confirm during scoping whether recruiting data exists and is in scope.

If Sympa was used to store client or partner organizations (not just internal employees), those records map to Crelate Company directly. Company name, domain, address, and primary contact map to their Crelate equivalents. Company size and industry map to custom fields if no default Crelate field applies.

Sympa HR workflows, approval chains, and employee self-service portal configurations do not have equivalents in Crelate and do not migrate as code. We audit and document every active Sympa workflow and approval rule in a written handoff inventory, mapping each to a recommended Crelate Automation or third-party HRIS configuration. The customer's HR admin or a Crelate partner rebuilds these post-migration.