Migrate from Built to Zoho Recruit

Built Employee records map to Zoho Recruit Candidate records. Each employee's first name, last name, email, phone, and job title transfer to the corresponding Candidate fields. Built's employment type (full-time, part-time, contractor) maps to a Zoho Recruit custom field since Candidate records do not have a native employment type property. Start date from Built transfers as a custom date field on the Candidate record. Candidates are created in the first migration pass before any referencing records are loaded.

Built Department records map directly to Zoho Recruit's built-in Department module, which is available on all paid tiers. Department name and code migrate as-is. Zoho Recruit's Department module is used to organize Job Openings by hiring team and to associate Candidates with their prospective department during the recruitment process.

Built Location records (office sites, remote-work designations) do not have a native equivalent in Zoho Recruit's standard schema. We create a Location picklist or multi-select field on the Job Opening module and populate it from Built's Location data. For Candidate records, Location maps to the Candidate's Address or a custom field depending on whether the candidate represents a remote hire or on-site placement.

Built stores job title as a free-text field on the Employee record. During migration to Zoho Recruit, the job title becomes the Job Opening Title and is used to populate the Candidate's Current Position or a custom field. Since both systems treat job title as free text, no transformation is required. If Built has structured job title data, we preserve it in a custom Candidate field for reporting.

Built's employment type enumeration (full-time, part-time, contractor, temporary) does not have a standard Zoho Recruit field on Candidate. We create a custom picklist field on the Candidate module and map the values directly. If the customer uses Zoho Recruit Professional or Enterprise, the custom field count ceiling (300 per module) accommodates this without constraint.

Built stores manager as an Employee-to-Employee self-lookup. Zoho Recruit's Candidate object has no native manager relationship field. We create a custom lookup field on Candidate pointing to the User or Contact record representing the hiring manager, resolved during the second migration pass using the destination-assigned Candidate IDs. If the manager is not a Zoho Recruit User, we store the manager name as a text field with a flag for admin review.

Built organizations can define custom properties on Employee records. We extract the full custom field schema via Built's API at the start of migration and compare against standard fields. Each custom field is created in Zoho Recruit with the equivalent data type (text, date, number, picklist, checkbox), then populated during data migration. Standard tier limits (50 fields per module) may require the customer to upgrade to Professional (300 fields) if the Built Employee schema is field-heavy.

Files and documents attached to Employee profiles in Built are excluded from the standard API export. We request a separate file-level export from Built support, extract attachments to a folder structure keyed by employee ID, and re-link them manually to the corresponding Candidate records in Zoho Recruit. Zoho Recruit's Attachments feature is enabled on Standard and above and supports PDF, DOC, and image formats up to the platform's file size limits.

Built's visual org chart is a rendering of underlying Employee hierarchy data, not a separate data object. We extract the underlying Employee and Manager relationship data during migration. The visual org chart itself does not migrate because Zoho Recruit is an ATS, not an org chart tool. If the customer needs org chart visualization in Zoho, they retain Built for that purpose or adopt a separate org chart solution. We flag this decision during scoping.

Built's ADP integration configuration is source-platform-specific and does not transfer to Zoho Recruit. If the customer continues using ADP for payroll, Zoho Recruit's integration options or a Zoho People ADP connector can be configured separately post-migration. We document the ADP field names and values that were synced into Built during the migration scope so the customer's Zoho admin can reproduce the integration configuration.

Built does not expose workflow or automation configurations via its API for extraction. We do not migrate Built automations as code. If Built contained any notification rules, approval chains, or automated org chart update triggers, we deliver a written inventory of these for the customer's admin to evaluate for rebuild using Zoho Recruit Workflow Rules (5 per module on Standard, 50 on Enterprise) or Custom Functions (Professional and above).

Built stores the employee's effective start date as a date field on the Employee record. We create a custom date field on the Candidate module (e.g., Original Hire Date) and populate it from Built. This preserves tenure history and is useful for organizations that convert former employees into Candidate records for re-hire tracking.