Migrate from Betterteam to Recruit CRM & ATS

Betterteam Job records map to Recruit CRM Job Positions. The job title, description, requirements, location, department, and status fields transfer directly. We map Betterteam's job status values (Active, Closed, Draft, Pending) to Recruit CRM's equivalent pipeline status. Active jobs migrate first so that application records have a parent position to reference at insert time. Archived and deleted jobs are excluded from the migration scope.

Betterteam stores candidate data flat per application rather than as unified profiles. We deduplicate candidate email addresses across all applications, reconstruct a single candidate record in Recruit CRM, and attach all application history to that profile. Betterteam properties including name, email, phone, address, and social URLs map to their Recruit CRM equivalents. Any candidate records exceeding Betterteam's Solo (25/month) or Plus (75/month) cap are flagged as overflow items and migrated first to ensure they land before the plan billing resets.

Betterteam Application records link a candidate to a job and include submission date, source job board, status (New, Reviewed, Liked, Declined), and any custom reviewer notes. We map the application status values to Recruit CRM pipeline stage values based on a status-mapping table defined during scoping. The source job board attribution (Indeed, LinkedIn, ZipRecruiter, etc.) transfers as a text field; granular UTM or campaign-level attribution is not available in Betterteam's export and cannot be reconstructed.

Betterteam's star-rating system (reviewers scoring candidates on a 5-star scale) migrates to Recruit CRM's candidate rating field. We preserve the numeric score and author attribution where available. If multiple reviewers rated the same candidate, we store the average score as the primary rating with individual reviewer scores preserved in the candidate notes field for audit.

Free-text notes attached to candidate profiles in Betterteam migrate to Recruit CRM candidate notes with author attribution and original timestamps preserved. We import notes in chronological order against the unified candidate profile, so the full review history is visible in Recruit CRM's timeline after migration. Notes that reference specific application IDs are remapped to the unified candidate record.

Resume files, cover letters, and supporting documents attached to Betterteam applications are downloaded, deduplicated by filename and hash, and re-uploaded to Recruit CRM's document storage linked to the corresponding candidate profile. Betterteam does not expose a folder structure, so all documents attach at the candidate level. We flag any oversized attachments (over Recruit CRM's 25 MB limit) for the customer's admin to review before upload.

Betterteam generates hosted careers pages as rendered HTML rather than structured data objects. We export the page URL and visible job listing content but cannot reconstruct the Betterteam-hosted page in Recruit CRM. Recruit CRM provides its own careers page builder. We document the existing Betterteam careers page URL and recommended steps for re-creating the listing in Recruit CRM's page builder as part of the post-migration handoff document.

Betterteam's job-to-board distribution mappings are stored server-side and are not exposed in any exportable API or field. We cannot migrate the distribution configuration. We deliver a written inventory of every active job board connected in Betterteam (as recorded in the job record's source-board field) and step-by-step re-connection instructions for Recruit CRM's job board integrations so the customer's admin can re-establish distribution after cutover.

Betterteam team members referenced on candidate records or application assignments map to Recruit CRM users by email address. We resolve the owner reference during import. Any Betterteam owner without a matching Recruit CRM user is placed in a reconciliation queue for the customer's admin to provision before candidate import resumes.

Betterteam custom fields on Jobs, Candidates, and Applications are identified during discovery and pre-created as equivalent custom fields in Recruit CRM before any data import. Betterteam's custom field types (text, number, date, dropdown) map to Recruit CRM's corresponding field types. Any unsupported field types are documented and resolved with the customer's admin before migration begins.