HRMS migration
Field-level mapping, validation, and rollback between Teamdoor and Recruit CRM & ATS. We move data and schema; workflows are rebuilt natively in Recruit CRM & ATS.
Teamdoor
Source
Recruit CRM & ATS
Destination
Compatibility
11 of 11
objects map 1:1 between Teamdoor and Recruit CRM & ATS.
Complexity
BStandard
Timeline
48–72 hours
Overview
Teamdoor organizes recruitment around a visual kanban board with candidate cards that track stage transitions, source channels, and team collaboration notes. Recruit CRM uses a traditional candidate database model with pipelines, tasks, and placements. The migration carries Teamdoor candidate records (including all resume files, interview notes, and stage history), job postings, talent pool segments, and custom fields into Recruit CRM's structured database. We handle the API extraction from Teamdoor on Pro/Enterprise plans and map Stage IDs to Recruit CRM pipeline stages. Workflows, email templates, and employer branding pages do not migrate — those require manual rebuild in Recruit CRM's builder tools. The delta-pickup window (24–48 hours) captures any candidates added or updated during the cutover window so the Recruit CRM database reflects Teamdoor's final state at go-live.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Teamdoor object lands in Recruit CRM & ATS, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Teamdoor
Candidate Card
Recruit CRM & ATS
Candidate
1:1Teamdoor's candidate card maps 1:1 to Recruit CRM's candidate profile. The card's stage history, source channel, and create date migrate as custom fields or activity log entries. Resume files re-upload to the candidate profile.
Teamdoor
Job Posting
Recruit CRM & ATS
Job
1:1Active job postings migrate as Recruit CRM jobs with title, description, requirements, and status. Closed or archived postings can be migrated as inactive jobs for historical reference or excluded based on your scope decision.
Teamdoor
Recruitment Stage
Recruit CRM & ATS
Pipeline Stage
1:1Teamdoor's kanban stages (Applied, Screening, Interview, Offer, etc.) map to Recruit CRM pipeline stages. Stage order and color coding are preserved. Teams with multiple pipelines in Teamdoor map each to a corresponding Recruit CRM pipeline.
Teamdoor
Talent Pool Tag
Recruit CRM & ATS
Candidate Tag
1:1Teamdoor talent pool tags migrate as Recruit CRM candidate tags. Multiple tags per candidate are preserved. Teams using tag combinations for segmentation should note that Recruit CRM uses flat tagging without hierarchy.
Teamdoor
Interview Note
Recruit CRM & ATS
Activity Log / Note
1:1Interview notes written on candidate cards migrate as notes or activity entries in Recruit CRM tied to the candidate. Original author, date, and note content are preserved. Formatting is converted to plain text or Recruit CRM's supported format.
Teamdoor
Source Channel
Recruit CRM & ATS
Source Custom Field
1:1Teamdoor tracks how candidates arrived (job board, direct link, referral, etc.). Recruit CRM has no native source field — we create a Source__c custom field on the candidate object and populate it from Teamdoor's channel data.
Teamdoor
Custom Collector Field
Recruit CRM & ATS
Custom Field
1:1Teamdoor's customizable candidate form fields map to Recruit CRM custom fields. Field type mapping: text fields to text, pick-lists to pick-lists, number fields to number. Multi-select collectors map to multi-select pick-lists where Recruit CRM supports them.
Teamdoor
Resume Attachment
Recruit CRM & ATS
Resume File
1:1PDF and Word resume files attached to Teamdoor candidate cards are downloaded and re-uploaded to Recruit CRM candidate profiles. File size limits apply (Recruit CRM default 10MB per file). We preserve the original filename and upload timestamp.
Teamdoor
Candidate Create Date
Recruit CRM & ATS
Original_Create_Date__c
1:1Teamdoor records the original application date. Recruit CRM's candidate creation date reflects the migration run. We preserve the Teamdoor original date as a custom datetime field for reporting continuity and compliance records.
Teamdoor
Stage Change Timestamp
Recruit CRM & ATS
Stage_Changed_At__c
1:1Teamdoor tracks when candidates move between kanban stages. This history migrates as a custom datetime field on the candidate record. Recruit CRM's pipeline stage does not retain stage-change timestamps natively.
Teamdoor
Teamdoor User / Owner
Recruit CRM & ATS
Recruit CRM User
1:1Teamdoor users matched to Recruit CRM users by email address. Unmatched users are flagged before migration. Records from unmatched users are assigned to a fallback Recruit CRM user or held for admin resolution.
| Teamdoor | Recruit CRM & ATS | Compatibility | |
|---|---|---|---|
| Candidate Card | Candidate1:1 | Fully supported | |
| Job Posting | Job1:1 | Fully supported | |
| Recruitment Stage | Pipeline Stage1:1 | Fully supported | |
| Talent Pool Tag | Candidate Tag1:1 | Fully supported | |
| Interview Note | Activity Log / Note1:1 | Fully supported | |
| Source Channel | Source Custom Field1:1 | Fully supported | |
| Custom Collector Field | Custom Field1:1 | Fully supported | |
| Resume Attachment | Resume File1:1 | Fully supported | |
| Candidate Create Date | Original_Create_Date__c1:1 | Fully supported | |
| Stage Change Timestamp | Stage_Changed_At__c1:1 | Fully supported | |
| Teamdoor User / Owner | Recruit CRM User1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Teamdoor gotchas
API access requires Pro tier or higher
Talent Pool OCR limits vary by plan
Pipeline stage schemas differ per job opening
Resume attachments are URL-referenced, not embedded
Employer branding pages cannot be migrated
Recruit CRM & ATS gotchas
API rate limits are license-scaled and can throttle bulk migration
Custom field schemas vary per organization and require field-level mapping
Files and email attachments require separate extraction and re-upload
Email sequences and automation logic do not transfer between platforms
Pair-specific challenges
Migration approach
Export Teamdoor data via API or CSV
We connect to the Teamdoor API on Pro or Enterprise plans to pull candidate records, job postings, talent pool tags, stage history, and custom field data. For Standard-tier accounts, we prepare a comprehensive CSV export covering all candidate fields and validate completeness before mapping begins. Resume files are downloaded in bulk from Teamdoor's attachment storage.
Map Teamdoor objects to Recruit CRM schema
We map Teamdoor's candidate cards, job postings, talent pool tags, and custom fields to Recruit CRM's candidate, job, and custom field objects. Stage names map to Recruit CRM pipeline stages. Custom collector fields in Teamdoor are created as custom fields in Recruit CRM before data import begins. A mapping plan is delivered for your review before any records move.
Create Recruit CRM custom fields and pipelines
Before loading data, we create the custom fields on Recruit CRM candidates and jobs to receive Teamdoor's source channel, stage-change timestamps, original create dates, and any other Teamdoor-specific properties. Pipeline stages are configured to match Teamdoor's kanban column names and order. This step is coordinated with your Recruit CRM admin if they prefer to create fields themselves.
Run sample migration with field-level validation
A representative slice of 50–200 records migrates first — covering candidates across different stages, jobs with varied status, and resumes. We generate a field-level diff between the Teamdoor source and the Recruit CRM destination so you can verify stage mapping, tag migration, and owner resolution before the full run commits.
Full migration with delta-pickup and audit log
The full dataset loads into Recruit CRM. A delta-pickup window (24–48 hours) captures any candidates added or stage-changed in Teamdoor during the cutover. An audit log records every operation. One-click rollback is available if reconciliation finds data gaps. Resume files upload concurrently with record creation.
Platform deep dives
Teamdoor
Source
Strengths
Weaknesses
Recruit CRM & ATS
Destination
Strengths
Weaknesses
Complexity grading
Standard HRMS migration. 1 of 7 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Teamdoor and Recruit CRM & ATS.
Object compatibility
1 of 7 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
7-object category — typical timelines run 2–7 days end-to-end.
API constraints
Teamdoor: Not publicly documented.
Data volume sensitivity
Teamdoor doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Teamdoor to Recruit CRM & ATS migration scoping. Not seeing yours? Book a call.
Walk through your Teamdoor to Recruit CRM & ATS migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Teamdoor
Other ways to arrive at Recruit CRM & ATS
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.
