Migrate from Voyse to Crelate

Voyse candidate and employee records map to Crelate Contacts. Given Voyse's dual ATS/onboarding role, we determine during discovery whether a record represents a job applicant (Contact in ATS mode) or an active employee (Contact with a custom employee_status__c flag). All Voyse standard fields (name, email, phone, address) map to Crelate Contact fields. Any Voyse custom properties require pre-creation in Crelate Settings > Core Records > Contacts before migration, including logical names for API mapping.

Voyse company or employer organisation records map to Crelate Company. The Crelate Company object serves as the parent for Contact records and supports industry classification, size, and revenue fields. We use company name as the dedupe key during import. If Voyse stores client companies separately from candidate employers, we maintain that distinction via a custom Voyse_organisation_type__c flag.

Voyse job postings or active positions map to Crelate Opportunity. The ATS pipeline stages (sourcing, screening, interview, offer, placed) map to Crelate Opportunity Stage values. We configure Crelate Record Types during schema design if the customer has multiple job categories. Opportunity title, description, and target hire date transfer to Crelate Opportunity fields.

Each Voyse onboarding or recruiting pipeline becomes a Crelate Record Type on Opportunity with a corresponding Sales Process that scopes stage values to the relevant recruiting workflow. Stage probability percentages are set per Crelate stage. If Voyse uses custom stage names, we create matching Crelate stage values during configuration.

Voyse stage transition history migrates as Task records attached to the parent Contact and Opportunity in Crelate, preserving the original timestamp, stage name, and transition reason. This requires careful date ordering to maintain the audit trail. We create a custom field voyse_stage_name__c on Task to carry the original Voyse stage label for reconciliation.

Voyse-uploaded candidate documents (CV, resume, cover letter, certifications) migrate as Crelate ContentDocument records linked to the Contact via ContentDocumentLink. We extract documents via Voyse's export mechanism (CSV URLs or direct file access determined during discovery) and upload them to Crelate's document store before linking. Document titles and file types are preserved.

Voyse custom properties on candidate/employee records require pre-creation in Crelate Settings > Core Records > Contacts before migration begins. We identify all Voyse custom fields during discovery, map them to Crelate field types (Text, Number, Picklist, Date, Boolean), create them in the destination Crelate org, then write migration scripts that target the new field logical names. Any Voyse multi-select or multi-checkbox properties map to Crelate multi-select picklists.

Voyse custom properties attached to job or position records are pre-created in Crelate as custom fields on the Opportunity object. Field type mapping follows the same rules as Contact custom properties. If a Voyse custom property references a Contact or Company lookup, we model it as an Opportunity lookup field and resolve the parent reference during migration.

Voyse assigned owners or recruiting users map to Crelate User records by email match. We extract the full owner roster from Voyse and match against Crelate's User table. Any Voyse owner without a matching Crelate User goes to a reconciliation queue for the customer's admin to provision before record import proceeds.

Voyse notes attached to candidate or job records migrate as Crelate Note records linked via ContentDocumentLink to the parent Contact or Opportunity. Rich text formatting is preserved. Note author and timestamp are carried into Crelate Note fields.

Voyse tasks or to-do items associated with candidates or jobs migrate to Crelate Task records. Status, Priority, due date, and assigned owner transfer to Crelate Task fields. We resolve task owners via the User email lookup before insert.

Voyse onboarding workflows and stage-specific automation do not migrate as executable code. Crelate's form builder and stage automation operate on a different event model. We deliver a written inventory of every active Voyse onboarding workflow, its trigger conditions, stage sequence, and required Crelate equivalent (custom forms, opportunity stage automation, or Crelate's built-in workflow tools). The customer's admin rebuilds these post-migration.