Migrate from Crelate to Zoho Recruit

Crelate Companies map directly to Zoho Recruit Clients. The Company name becomes Client Name, website maps to Website, and address fields map to Zoho's address composite. We import Companies first so that downstream Contacts and Job Openings can reference a valid Client lookup during load. If a Crelate Company has no name, we substitute the primary domain as the Client Name and flag the record for manual review in Zoho.

Crelate Contacts map to Zoho Recruit Candidates. The primary fields (name, email, phone, address) transfer directly. Last Name is mandatory in Zoho Recruit; if a Crelate Contact has no last name, we substitute the first name or a placeholder value and flag the record. Custom fields on Crelate Contacts transfer to Candidate custom fields up to Zoho's module allowance (50 on Standard, 300 on Enterprise). Any Crelate custom fields exceeding the cap are ranked by usage frequency during scoping and brought forward within the limit; the remainder are documented for the customer's admin to create in Zoho post-migration.

Crelate Jobs map to Zoho Recruit Job Openings. Job title, description, and status transfer directly. The Job-to-Company linkage maps to the Client lookup in Zoho Recruit; we resolve the Zoho Client ID at migration time using the Company name as a dedupe key. Pipeline stage names from Crelate transfer to Zoho Job Opening stage values and are preserved in the same order.

Crelate Opportunities map to Zoho Recruit Job Openings in the staffing-agency context where Opportunities represent client job orders. The Opportunity amount and stage map to the Job Opening fee and status. If the Crelate data model uses Opportunities for business development rather than job orders, the mapping shifts to Zoho's client-engagement tracking; this is clarified during scoping.

Crelate Placements record placed candidates and capture salary, pay rate, start date, and fee percentage. We migrate Placements only after confirming that both the parent Job and Candidate exist in Zoho Recruit with resolved IDs. The placement fee and pay rate map to Zoho's candidate record custom fields or to linked Job Opening properties depending on the customer's configuration choice made during scoping.

Crelate custom fields on Contacts, Companies, and Opportunities transfer to Zoho Recruit Candidate, Client, and Job Opening custom fields. Crelate's 20-field per-entity cap requires a ranked field inventory before migration; we surface this during discovery and exclude fields beyond the cap with a written list delivered for manual creation in Zoho post-migration. Zoho Standard's 50-field allowance accommodates most Crelate schemas without reduction.

Crelate Activities (calls, emails, meetings, tasks linked to Contacts and Companies) map to Zoho Recruit Tasks, Calls, Events, and Notes. Activities are gated behind a Crelate tier add-on; we verify the source plan includes Activity access during scoping. Zoho Standard includes Tasks, Calls, Events, and Notes. Activity date and description transfer; linked Contact and Company references resolve to Candidate and Client IDs at migration time.

Documents attached to Crelate Contacts, Companies, Jobs, or Placements export via the API or bulk export tool and re-upload to Zoho Recruit as attachments on the corresponding Candidate, Client, or Job Opening record. Document folder structure does not transfer; we attach files to the parent record only. Files larger than 25 MB split into chunks before Zoho upload per Zoho's file size limit.

Crelate tags applied to Contacts, Companies, and Opportunities transfer to Zoho Recruit tags on the equivalent record. Tags with special characters or length exceeding Zoho's limit are sanitized during transform. The customer selects tag strategy during scoping if any ambiguity exists about whether tags represent categorical labels or workflow markers.

Crelate Users who own records map to Zoho Recruit Users by email address match. We extract every distinct owner referenced on Contacts, Companies, Jobs, and Opportunities and reconcile against Zoho's User table. Users without a matching Zoho account enter a provisioning queue for the customer's admin to create before the migration resumes. Active versus inactive status preserves from Crelate.

Crelate Opportunity and Job pipeline stages transfer to Zoho Recruit Job Opening stage values. Stage names and ordering are preserved exactly; stage-specific automation (triggers on stage change) do not migrate as code. We deliver a written stage map documenting the original names and order so the customer's admin can configure any Zoho workflow rules against the correct stage values.

Crelate Sequences encode automated outreach cadences with templated emails, tasks, and timing rules. This is a platform-native feature that cannot be exported as a portable artifact. We document the Sequence definitions (trigger, steps, delays, and action sequence) during migration discovery and deliver a written inventory for the customer's admin to rebuild in Zoho using Zoho Recruit Workflow Rules or Blueprint. We do not migrate Sequences as data.