Migrate from Fountain to Crelate

Fountain's Applicant records map to Crelate Candidate records. We preserve contact details (name, email, phone, address), hiring source attribution, and the original Fountain application date as a custom field fountain_applied_date__c for audit. Fountain's application status maps to Crelate's pipeline stage sequence. Applicant records with no email address are flagged for manual review before import because Crelate requires a primary email for deduplication. Any readOnly custom attributes on Fountain Applicants cannot be written to Crelate as editable values; we identify these during discovery, exclude them, and document them for the customer to map to Crelate custom fields with appropriate defaults.

Fountain Job Posts map to Crelate Job records. We preserve job title, description, requirements, employment type (full-time, part-time, hourly), and the linked department assignment. Fountain's job-specific custom attributes migrate to Crelate custom fields on Job. Crelate's Job object also stores the pipeline configuration that we map from Fountain's stage definitions. The Fountain location assignment on a Job Post maps directly to the location on the Crelate Job record.

Fountain stage definitions (stage names, sequence order, configured automations) cannot be extracted via API and do not migrate as code. We document the active stage names and their sequence from Fountain during discovery and use that documentation to configure equivalent Crelate pipeline stages. Fountain's conditional stage transitions (automated rules for advancing candidates based on criteria) are captured in the written automation inventory for manual rebuild in Crelate's workflow builder. Stage probabilities migrate as static values where defined in Fountain.

Fountain Locations map directly to Crelate Locations. We preserve location name, address, and any location-specific notes. Fountain's Location hierarchy (locations grouped by region or area) maps to a flat location structure in Crelate, and we document any hierarchy flattening during scoping so the customer admin can configure region groupings in Crelate if needed. Location assignment on Applicant records resolves to the Crelate Location reference at migration time.

Fountain Departments map to Crelate Departments. We preserve department name and the department-to-location assignment relationships. Fountain's multi-department hierarchy flattens to Crelate's single-level Department object, and we document the hierarchy mapping so the customer can optionally re-create parent-child relationships in Crelate's organization structure. Department assignments on Job Posts map to the Crelate Department reference at migration time.

Fountain Offer records (compensation, start date, offer status) map to Crelate Offer records linked to the migrated Candidate. We preserve offer salary or hourly rate, shift schedule details, start date, offer status (extended, accepted, declined, withdrawn), and any offer-specific notes. The Candidate reference is resolved by matching the Fountain Applicant ID to the migrated Crelate Candidate record. Offer history (if a candidate had multiple offers) migrates as separate Offer records in sequence order.

Fountain Notes attached to Applicants migrate to Crelate Notes on the migrated Candidate record. We preserve note content, author attribution (mapped by email to Crelate user), and original creation timestamp. Fountain Notes are unstructured text blobs without separate fields for disposition or interview rating; these map as plain text notes with the author attribution providing context. Notes are imported after the parent Candidate record is confirmed in Crelate to maintain the link.

Fountain's document attachments (hiring forms, certifications, background check results) migrate as file attachments on the corresponding Crelate Candidate record. Fountain stores documents separately from applicant records and requires individual API calls per attachment. We export documents in parallel batches, maintain a filename-to-applicant-ID mapping table, and upload each file to the correct Crelate Candidate record. Large document volumes (over 50,000 files) increase migration duration and should be scoped explicitly before starting. We recommend excluding very large binary files (video interviews, audio recordings) from the standard migration scope as a separate file transfer.

Fountain custom attributes on Applicants and Jobs map to Crelate custom fields. We identify all custom attributes during discovery, map their data types to the closest Crelate field type (text, number, date, picklist, checkbox), and pre-create the custom fields in Crelate before migration. Any Fountain custom attribute with readOnly=true is flagged and excluded from import because Crelate's API cannot receive values for fields that are system-populated. readOnly attributes are documented with their current values so the customer's admin can either set static defaults or configure Crelate calculated fields to replicate the logic.

Fountain's automation rules (auto-advancing candidates, email triggers, task creation per stage, conditional stage transitions) are not exposed via Fountain's public API and cannot be extracted programmatically. We perform a manual discovery process during scoping where we document every active automation configuration including its trigger event, conditions, actions, and affected stages. This written automation inventory is delivered as part of the migration scope, and the customer's Crelate admin rebuilds the equivalent rules in Crelate's workflow builder post-migration. This is standard scope for Fountain migrations and adds post-migration configuration time that should be accounted for in project timelines.

Fountain tracks hiring source attribution (where each applicant came from) at the Applicant level. We preserve the original source value (job board, employee referral, direct apply, agency) on the Crelate Candidate record and populate the Crelate sourcing activity history to reflect the Fountain application event. This preserves the reporting continuity that teams rely on for hiring source ROI analysis across the migration cutover.

Fountain Owners (hiring managers, recruiters, coordinators) referenced on Applicant and Job records map to Crelate User records. We resolve owners by email match. Any Fountain Owner without a matching Crelate User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Owner assignment on Job Post records and on Offer records migrates by resolving the same Fountain Owner-to-Crelate User mapping table.