Migrate from Fountain to Recruit CRM & ATS

Fountain Applicant records map directly to Recruit CRM Candidate records. The Fountain applicant ID is preserved as an external reference field for reconciliation. Contact details (name, email, phone, address) map to standard Candidate fields. Fountain's appliedAt timestamp migrates to Recruit CRM's creation date. Application source attribution (referral channel, job board, direct) migrates as a Candidate tag and as a custom field for reporting. Candidates are imported before Jobs so that the Job lookup is satisfied at insert time.

Fountain Job Posts map to Recruit CRM Job records. Job title, description, and requirements transfer to standard Job fields. The Fountain Job's linked Location and Department assignments are preserved as tags on the Job record. Fountain's job status (open, closed, archived, drafted) maps to Recruit CRM's Job status field. Job Owner (recruiter assignment) maps to Recruit CRM's assigned recruiter field via email matching against the destination User table.

Fountain pipeline stages map to Recruit CRM pipeline stage values on the Candidate record. Stage sequence order is preserved from Fountain's stage configuration. Fountain's conditional stage transitions (automated rules for skipping or branching) are documented for manual rebuild in Recruit CRM's stage builder; they do not migrate as executable code. Probability weights from Fountain stage settings are noted as reference values for the customer's Recruit CRM admin to configure against the Kanban pipeline.

Fountain Locations represent physical hiring sites (stores, warehouses, restaurants) and do not have a direct Recruit CRM equivalent since Recruit CRM organizes hiring by Client and Candidate rather than by geographic site. We map Fountain Locations to Candidate tags and Job tags so that multi-site operations retain location attribution. Location address data migrates as a custom field on the Candidate or as part of the candidate's work authorization region. This mapping requires a decision during scoping on whether to tag by Location, Department, or both.

Fountain Departments group Jobs and hiring teams by business function and are preserved as tags on Job and Candidate records in Recruit CRM. Department hierarchies (parent-child) are flattened to a flat tag set unless Recruit CRM's custom fields are configured to support a hierarchical representation. We document the full department tree during discovery for the customer to decide the appropriate Recruit CRM representation.

Fountain user-added Notes on Applicants are text content attached to a Candidate record in Recruit CRM as a note block with author attribution and timestamp. Notes are migrated in creation-date order so that the candidate's narrative timeline is preserved. Recruit CRM does not have a separate Notes object equivalent to some ATS platforms; notes attach directly to the Candidate record and appear in its activity feed.

Fountain customAttributes on Applicants (certification flags, shift preferences, availability windows, background check status, source-specific qualifiers) map to Recruit CRM custom fields. We create the corresponding custom fields in Recruit CRM during the schema design phase before data load. Attributes with Fountain's readOnly flag set to true cannot be written as editable values in Recruit CRM; we flag these during discovery and suggest either excluding them or mapping them to Recruit CRM custom fields with default values for manual completion post-migration.

Fountain document attachments (hiring forms, compliance certifications, background check results, signed agreements) are stored in Fountain's separate document store and retrieved via individual API calls. We export documents in parallel batches, maintaining a filename-to-applicant-ID lookup table, and attach them to the corresponding Candidate record in Recruit CRM using the standard file upload API. Large document volumes increase migration duration and must be scoped explicitly before kickoff; we recommend a pre-migration document count audit to set accurate timeline expectations.

Fountain Offer records containing compensation details, start dates, offer status, and shift schedule map to Recruit CRM as structured fields attached to the Candidate record or as a candidate custom section. Offer status (extended, accepted, declined, rescinded) migrates as a custom picklist field. Salary, hourly rate, and shift details transfer to the corresponding compensation fields. We preserve offer history including all status changes and timestamps.

Fountain's automation rules (auto-advancing candidates through stages, email triggers per stage, task creation on stage entry, SLA timers, and conditional routing) are not accessible through the Fountain public API and cannot be extracted programmatically. We do not migrate these as executable code. During discovery we document every active Fountain workflow configuration including its trigger conditions, actions, and stage dependencies, and we deliver a written rebuild guide mapped to Recruit CRM's no-code workflow automation builder. This document is the handoff artifact for the customer's admin to reconstruct active hiring logic in Recruit CRM post-migration.