Migrate from Fountain to Zoho Recruit

Fountain's Applicant records map directly to Zoho Recruit's Candidate module. Each Applicant's contact details (name, email, phone, address) map to the corresponding Candidate fields. Fountain's applicant status (Applied, Screening, Interview, Offer, Hired, Rejected) maps to Zoho Recruit's Candidate Status picklist values, which we configure during schema setup to match Fountain's stage names. Note: Fountain applicants without a last name will be rejected by Zoho Recruit because Last Name is mandatory; we flag these during discovery and insert 'Not Provided' as a placeholder so the record is not dropped during import.

Fountain Job Posts map to Zoho Recruit Job Openings. The Job Post's title, description, requirements, and department assignment migrate as Job Opening fields. Fountain's linked Location assignment maps to Zoho Recruit's Department or a custom Location field, depending on the customer's hierarchy preference. Active Job Post status maps to Zoho Recruit's Open status; archived or closed posts map to Closed with a custom archive_date field.

Fountain's pipeline stages (e.g., Applied, Phone Screen, Interview, Offer, Hired) are not objects but configurable values on Job Posts. We extract the stage sequence from each Job Post's pipeline configuration, then create corresponding stage values in Zoho Recruit's Hiring Pipeline. Fountain's conditional stage transitions and automated actions per stage are documented as part of the automation inventory and are not migratable as code; they require manual configuration in Zoho Recruit's Workflow Rules after migration.

Fountain Locations represent physical work sites with addresses and location-specific hiring rules. We migrate location names and addresses as either Zoho Recruit Department records (if the customer uses department-based organization) or as entries in a custom Location module that we pre-create during schema setup. The choice is made during scoping based on the customer's reporting and filtering needs in Zoho Recruit.

Fountain Departments map directly to Zoho Recruit's Department object. We preserve department assignments on Job Posts so that hiring manager filtering and reporting by business unit remain consistent after migration. If Fountain uses nested department hierarchies, we flatten them into Zoho Recruit's single-level Department structure with a custom parent_department__c field to maintain the hierarchy for reporting.

Fountain Offer records (compensation details, start dates, offer status tied to specific Applicants) map to Zoho Recruit's Offer module. Salary, shift schedule, position details, and offer status migrate as Offer fields linked to the corresponding Candidate. Zoho Recruit's Offer Letter Templates (50 on Standard, 100 on Enterprise) can be associated with migrated offers post-migration; the templates themselves are not migratable and are documented for rebuild.

Fountain customAttributes on Applicants and Jobs migrate to Zoho Recruit custom fields on the corresponding module. We identify all customAttributes during discovery, map their data types to Zoho Recruit field types (Text, Picklist, Checkbox, Date, Number), and create the fields before import. Fountain's readOnly attributes (system-controlled fields that cannot be set via API) are flagged and mapped either to Zoho Recruit read-only fields or to custom display fields with a system-populated default value, because Zoho Recruit has no direct equivalent of Fountain's readOnly flag at the API level.

Fountain's document attachments (hiring forms, certifications, background check results, offer letters) are stored separately from Applicant records and require individual API calls to retrieve. We export documents in parallel batches, maintaining filename-to-applicant-ID mapping, then upload each file to Zoho Recruit's Attachments section on the corresponding Candidate record. Large document volumes increase migration duration and must be scoped explicitly; we recommend a document-only dry run with a sample of 50 records before committing to the full volume.

Fountain Notes on Applicants (hiring manager context, interview feedback, internal commentary) are text blobs with author and timestamp. We migrate note content and attribution to Zoho Recruit Notes linked to the corresponding Candidate record. Zoho Recruit Notes do not support the same rich formatting options as some ATS platforms, so we preserve the plain-text content and include the author name and timestamp in the Note body to maintain full context.

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 document every active workflow configuration during discovery by reviewing Fountain's pipeline settings with the customer's admin, and we deliver a written inventory of each automation with its trigger, conditions, actions, and the equivalent Zoho Recruit Workflow Rule configuration. The customer's admin rebuilds the workflows in Zoho Recruit post-migration; we do not rebuild them as part of the migration scope.

Fountain tracks where each applicant originated (Indeed, referrals, direct apply, job board) as part of the Applicant record. We migrate the source attribution to Zoho Recruit's Candidate Source field on each record. If Fountain uses custom source channels beyond the standard list, we create matching custom picklist values in Zoho Recruit during schema setup so reporting by sourcing channel remains consistent.

Fountain's hiring team members (recruiters and hiring managers assigned to Jobs and Applicants) map to Zoho Recruit User records. We resolve owners by email match against the destination Zoho Recruit User table. Any Fountain Owner without a matching Zoho Recruit User goes to a reconciliation queue for the customer's admin to provision before record import resumes, because Zoho Recruit requires a valid OwnerId on candidate records.