Migrate from Beamery to Zoho Recruit

Beamery Contacts map to Zoho Recruit Candidates, which is the primary candidate record. We map all standard fields (name, email, phone, title, location) plus Beamery custom fields. Multi-select custom fields in Beamery use semicolon delimiters; Zoho Recruit also expects semicolons for multi-select picklist values in CSV imports, so the delimiter convention carries over without transformation. The Beamery contact type (active candidate vs talent pool member) is preserved in a custom field beamery_contact_type__c on the Candidate record.

Beamery Contacts that represent hiring manager or client relationships (if tracked in Beamery) map to Zoho Recruit Contacts under the Staffing Agency module. We distinguish Contacts from Candidates during scoping by inspecting the contact_type property or pool assignment history. Candidate-to-Contact linking in Zoho Recruit (associating a candidate with a client) is preserved as a custom lookup field if the relationship existed in Beamery.

Beamery Talent Pools have no native Zoho Recruit equivalent. We resolve this by creating a Zoho Recruit Tag for each Beamery Talent Pool, then applying the corresponding Tag to all Candidate records that held membership. Pool membership dates are stored in a custom Candidate field pool_joined_date__c per pool. If a Contact belongs to multiple pools, all corresponding Tags are applied. This preserves the relationship-centric view of talent pools without requiring a custom object.

Beamery Vacancies map to Zoho Recruit Job Openings. Vacancy metadata (title, department, location, status) migrates directly. The pipeline stage names and pipeline structure require per-tenant mapping because Beamery's Convert Flow pipeline stages are tenant-defined and Zoho Recruit's Hiring Pipeline stages are configurable but use a different default set. We collect the customer's stage name mapping during scoping and configure Zoho Recruit pipeline stages before migration.

Beamery Campaigns (outbound engagement sequences) migrate as Zoho Recruit email templates plus the associated Candidate tag indicating campaign membership. Send dates and engagement events (opened, clicked, replied) are preserved as Activity Log entries on the Candidate record. The campaign automation logic (Recipe-driven triggers and conditional routing) is not portable; we document each active Beamery Recipe with its trigger, conditions, and recommended Zoho Recruit Workflow Rule equivalent as a separate handoff document.

Beamery Skills taxonomy entries attached to Contacts migrate as Zoho Recruit Tags on the Candidate record. Each unique Beamery skill value becomes a Tag. If a Contact had multiple skills assigned, all corresponding Tags are applied. The Beamery skills taxonomy is customer-defined and may contain hundreds of unique values; we deduplicate and normalize before creating Tags to avoid tag explosion in Zoho Recruit.

The Beamery Vacancy-to-Candidate linkage (which candidates applied to or were added to which Vacancy) maps to Zoho Recruit's Job Opening to Candidate association via the Candidate Stage field. We preserve the original Vacancy reference as a custom field vacancy_original_id__c on the Candidate for audit trail and reporting continuity.

Beamery Users (recruiters and sourcers) are exported by email and mapped to Zoho Recruit Users provisioned by the customer's admin before migration. Owner assignments on Contact, Talent Pool, and Vacancy records resolve via email match. Any Beamery User without a corresponding Zoho Recruit User goes to a reconciliation queue; migration cannot proceed for those records until the admin provisions the missing User. Zoho Recruit requires at least two active Users in the account before CSV import can proceed.

Beamery Convert Flow form submissions (candidate data captured through forms) migrate as Candidate records with a custom field convert_flow_name__c indicating the source form and conversion_timestamp__c preserving the original conversion date. The form configuration itself (field layout, conditional logic, downstream actions) is not portable and must be rebuilt as a Zoho Recruit Web Form. We document the full Convert Flow field set and conditional rules during scoping for the admin to use as a rebuild reference.

Beamery engagement events (emails sent, page views, notes, calls, meetings) are timestamped activities linked to Contacts. We export them as Zoho Recruit Task, Call Log, Event, or Note records linked to the corresponding Candidate. Zoho Recruit's Corporate plan limits exports to 20,000 records per module per export request; for large engagement histories we run paginated export batches. Activity ordering is preserved by setting the Zoho Recruit activity date to the original Beamery timestamp.

Binary attachments (resumes, portfolio files) stored in Beamery are exported as file metadata with URL references. We include resume file name, file size, and upload date in custom Candidate fields. If Beamery's file storage is accessible via the API, we retrieve and re-attach the file to the Zoho Recruit Candidate record. If storage access is unavailable, we flag the record for the customer to re-upload manually after migration.

Beamery Tags are flat label fields applied to Contacts. They map directly to Zoho Recruit Tags on the Candidate record with a one-to-one label mapping. The Zoho Recruit Enterprise plan supports up to 1,000 tags; we check tag count against the target plan during scoping to avoid hitting the limit with large taxonomy exports.