Migrate from Serviceform to Zoho CRM

Serviceform Leads with qualification status (e.g., qualified, unqualified, new) map to Zoho CRM Lead records by default. For leads that have progressed through the Serviceform AI qualification flow and are confirmed buyers, we map them to Zoho Contact records attached to an Account. The split rule is defined during scoping based on Serviceform's lead_score and status properties. The original qualification score migrates as a custom field zf_original_score__c on the Lead or Contact for audit.

Serviceform conversation logs (visitor messages, bot responses, timestamps, channel metadata) migrate to Zoho CRM as Activity Task records (for the engagement record) plus Notes (for the transcript body). The channel metadata (web, SMS, email) becomes a custom field on the Task. ActivityDate preserves the original timestamp. Full transcript preservation is optional and affects extraction scope; we discuss with the customer whether summary transcripts (last message per thread) or full logs are required during scoping because the extraction volume changes.

Serviceform form definitions (field configurations, labels, types) migrate as a Zoho CRM custom module (e.g., Form_Submissions__c) with custom fields matching the original schema. Conditional logic on field visibility and routing is documented as a written specification during extraction and handed off for rebuilding in Zoho's form builder or a custom Deluge script. Form submission records migrate as rows in the custom module with a lookup to the related Lead or Contact.

Serviceform chatbot flows (nodes, intents, response rules, conditional branching) are exported as a structured configuration document rather than migrated as executable logic. The export includes node structure, intent mappings, and response trees. We deliver this as a written chatbot inventory with screenshots and flow diagrams for the customer's Zoho admin to rebuild using Zoho's Blueprint, workflow rules, or Zoho SalesIQ if live chat functionality is required in the destination.

Serviceform user accounts with roles and seat assignments map to Zoho CRM User records by email match. Role assignments (admin, agent, viewer) map to Zoho Roles and Profiles. Active versus inactive status on Serviceform determines whether the Zoho User is provisioned as active or inactive. We reconcile owners on Leads, Contacts, and Deals during migration by resolving the Serviceform agent email to the Zoho User ID.

Serviceform integration connections (CRM sync, email, analytics tools) are preserved as a list of active integration names and connection configurations. We do not migrate integration credentials or reconnect them in Zoho. The inventory is delivered as a written list for the customer's admin to reconfigure in Zoho's Connected Apps, Zoho Flow, or Zapier depending on the integration type.

Serviceform ATS module data (applicant profiles, resume files, ranking scores) is extracted as a separate data set from core chatbot and lead data. Applicant records migrate to a Zoho custom module (Applicants__c) with fields for candidate name, email, phone, resume file (uploaded as attachment), and ranking score. If the customer licenses Zoho Recruit, we map to its Candidates module instead. Resume file formats are converted to PDF if the source format is not directly supported by Zoho's file upload.

Serviceform live chat session logs (visitor info, agent assignment, session duration, resolution status) migrate to Zoho CRM Task records with a custom field for session status (Active, Resolved, Pending Follow-up). The agent assignment resolves via email match to the Zoho User. Sessions without an assigned agent are imported with no OwnerId and flagged for manual assignment.

Serviceform AI agent Mira generates a lead qualification score stored as a property on the Lead record. We extract this value and migrate it as a custom numeric field (lead_score__c) on the Zoho Lead or Contact. If the customer plans to use Zoho's AI assistant Zia for predictive scoring, we document the original Serviceform scoring model as a reference so that the Zia model can be calibrated to produce comparable results.

Individual form submission records from Serviceform migrate as rows in the Form_Submissions__c custom module. Each submission links to the originating Lead or Contact via a lookup relationship. Submission timestamp becomes ActivityDate on the related Task. We extract submission metadata (form name, submission ID, UTM parameters if available) as additional fields in the custom module to preserve source attribution.