Migrate from Fountain to BambooHR

Fountain Applicants map directly to BambooHR Applications. We preserve applicant contact details (name, email, phone, address), work history answers, screening responses, and the current stage assignment. The original Fountain stage name is stored in a custom BambooHR field (fountain_stage__c) so that hiring managers retain context about where in the Fountain pipeline each candidate was when migrated. Fountain's applicant source attribution (referral channel, job board, direct) migrates to BambooHR's application source field.

Fountain Job Posts map to BambooHR Jobs. Job title, description, requirements, department assignment, and location linkage migrate directly. Fountain's pipeline configuration (stage sequence) does not map automatically to BambooHR's application status model; we document the stage sequence during discovery so your team can configure BambooHR statuses to match the original hiring workflow. Closed and archived Fountain jobs migrate with their final disposition preserved.

Fountain Stages map to BambooHR Application Status values. Each Fountain pipeline has its own stage sequence, and BambooHR supports multiple status categories per job. We map the stage names and order, and note any conditional stage transitions that cannot be represented in BambooHR's flat status model. Auto-advance rules that trigger stage movement in Fountain are documented separately as they require manual rebuild in BambooHR.

Fountain Locations (physical work sites: stores, warehouses, restaurants) map to BambooHR Locations if your BambooHR plan includes multi-location setup, or to the location address fields on the Company Information page for single-location accounts. We preserve location names, addresses, and the hiring team assignments associated with each site. Multi-location hierarchies where Fountain organizes sites under regions or districts require reparenting in BambooHR's organizational structure.

Fountain Departments map directly to BambooHR Departments. Department assignments on Job Posts and Applicants migrate to BambooHR department records so that reporting by business unit remains consistent. Fountain's department hierarchy (parent-child groupings) maps to BambooHR's department nesting structure. We resolve any department IDs referenced on Job Posts before importing Jobs into BambooHR.

Fountain Offer records (compensation details, start date, offer status) migrate as fields on the corresponding BambooHR Application record. Offer letter documents attach to the Application as file uploads. BambooHR does not have a standalone Offer object; offer metadata lives on the Application record or in a custom section. We flag any offer status values that do not map to BambooHR's standard application status set and document the gap for your team.

Fountain Notes attached to Applicants migrate to BambooHR Application Notes. Note content and author attribution (user name and timestamp) transfer directly. Notes are imported after the parent Application record exists so that the relationship is satisfied at insert time. Fountain's internal feedback ratings on notes do not map to a BambooHR equivalent and are documented in the notes field as plain text.

Fountain customAttributes on Applicants and Jobs migrate to BambooHR custom fields where the attribute is not marked readOnly. ReadOnly attributes (system-controlled fields with the readOnly flag set to true) cannot be written via Fountain's API and therefore cannot be extracted for migration; we flag these during discovery and recommend either excluding them or creating equivalent BambooHR custom fields with system-populated defaults. Hidden attributes are excluded from migration scope.

Fountain document attachments (hiring forms, compliance certifications, background check results) migrate as file attachments to the corresponding BambooHR Application record. Each document requires an individual API call to retrieve from Fountain, so we export documents in parallel batches and maintain a filename-to-applicant-ID mapping table. Large document volumes increase migration duration significantly and should be scoped explicitly before kickoff.

Fountain automation rules (auto-advance candidates, email triggers, task creation per stage) are not exposed via Fountain's public API and cannot be exported programmatically. We document every active Fountain Workflow during discovery, capturing the trigger conditions, stage transitions, email templates, and task actions. BambooHR Workflows and approval chains in the HR module serve as the rebuild target. Your team or a BambooHR partner rebuilds the automations post-migration based on the documented inventory.