Migrate from Teamdoor to Crelate

Teamdoor candidates map directly to Crelate Contacts. Crelate's Contact record stores name, email, phone, title, address, and custom fields. Candidate IDs from Teamdoor are preserved as Source_System_ID__c custom field on the Crelate Contact for traceability, delta-run de-duplication, and cross-referencing between Teamdoor records and their migrated Crelate counterparts after the migration completes.

Teamdoor companies that represent hiring clients map 1:1 to Crelate Companies. Crelate's Company record stores name, website, industry, phone, and address. Teamdoor company hierarchies (parent/child) are not natively supported in Crelate; we flatten them and store the parent reference as a custom text field on the child Company record.

Teamdoor job requisitions map to Crelate Jobs. Crelate Job records store title, description, status (Open/Closed/Filled), location, and salary range. We map Teamdoor's job status values to Crelate's Open/Closed/Filled status and preserve the original posted date as a custom datetime field.

Teamdoor applications (candidates applied to jobs) map to Crelate Opportunities because Crelate Opportunities represent the placement relationship between a Contact and a Job/Company. Source candidate ID and job ID are stored as custom fields on the Opportunity for linkage traceability.

Teamdoor's Kanban pipeline stages (Applied, Screening, Interview, Offer, Hired) have no native Crelate equivalent, so we create a custom pick-list field called Pipeline_Stage__c on the Crelate Contact record. Original stage-entered timestamps are preserved as Pipeline_Stage_Entered_Date__c custom datetime fields to maintain audit continuity and allow reporting on stage-transition timing after migration.

Teamdoor talent pool classifications (e.g., 'Passive Candidate', 'High Priority', 'Referred') are stored as tags on the candidate record. We map these to a custom pick-list field Talent_Pool_Classification__c on the Crelate Contact. Multiple classifications per candidate are stored as comma-separated values in the custom field.

Teamdoor allows recruiters to assign a star rating (1-5) to candidates, which is stored as a numeric value on the candidate record. Crelate has no native star-rating field, so we create a custom pick-list field Teamdoor_Rating__c on the Crelate Contact and map the numeric rating value directly to preserve the original rating data for reporting purposes.

Teamdoor candidate notes and interview notes map to Crelate Notes attached to the Contact record. We preserve the original created date as Note_Original_Date__c and the note author name. Crelate does not support rich-text formatting in Notes; plain text is migrated as-is.

Teamdoor tags applied to candidates map directly to Crelate Tags, which serve as a shared classification vocabulary across Contact, Company, Job, and Opportunity records. Tags with identical names merge during the load process, and we flag any duplicate tag names before loading to prevent unintended merging of distinct classifications.

Teamdoor resume files attached to candidates are re-uploaded as Crelate Documents linked to the Contact record. File size limits follow Crelate's storage tier (15GB default on Business). We map the original filename and attach it to the correct Crelate Contact by matching on candidate email.

Teamdoor employer-branding career pages (custom logo, banner, copy, and company description) are platform-hosted assets with no structured export format available from Teamdoor's API or data export tools. These cannot be migrated programmatically and must be rebuilt manually in Crelate's Settings | Job Portal Branding after migration using the documented Teamdoor asset specifications.

Teamdoor's multi-channel job board posting configuration — specifying which boards (Indeed, 104, LinkedIn), which jobs, posting schedules, and authentication credentials — is stored as platform integration settings, not as candidate or job data. Each job board integration must be reconfigured from scratch in Crelate's Settings | Integrations page after migration.

Teamdoor workflow triggers and automation rules do not migrate. Crelate has its own Automation and Sequencing tools (available on Business Plus) that must be rebuilt. We provide a structured export of Teamdoor's workflow definitions as a reference document for your Crelate admin to use during rebuild.