Migrate from Serviceform to Freshsales

Serviceform Leads with a qualified status from AI agent Mira or high chatbot interaction scores map to Freshsales Contact with an associated Account. Unqualified leads (low score, form-only submissions with no conversation) map to Freshsales Lead for follow-up qualification. We preserve Serviceform's lead score in a custom field sf_lead_score__c on both Lead and Contact for Freddy AI training and reporting alignment.

Serviceform conversation logs (visitor messages, bot responses, timestamps) migrate as Freshsales Notes linked to the parent Contact or Lead, preserving the full transcript as a chronological note body. We extract conversation metadata (channel, duration, resolution status) and write them to custom Task fields for activity reporting. The original Serviceform conversation timestamp becomes the Note created date for timeline accuracy.

Serviceform form submission data maps to Freshsales Contact custom fields by field name matching. Fields with no matching custom field on the destination are written as a Note attached to the Contact summarizing the original form submission. Conditional logic rules on Serviceform forms are documented separately as a Workflow rebuild specification; the logic does not transfer automatically to Freshsales.

Serviceform chatbot flows (nodes, intents, response rules) do not have a direct Freshsales equivalent because Freshsales uses a different automation model. We export the chatbot flow structure and conversation tree as a written specification document that your admin uses to rebuild equivalent routing logic using Freshsales' Workflow builder. This document is delivered as part of the migration handoff package.

Serviceform user accounts with roles and seat assignments map directly to Freshsales User records. We match by email address. Any Serviceform user without a matching Freshsales User goes to a reconciliation queue for your admin to provision before the Contact import phase.

Serviceform ATS applicant records (resume files, candidate profiles, ranking data) migrate as Freshsales Contacts with a custom record type ATS_Candidate and associated custom fields for ranking and status. Resume files transfer as ContentDocument records attached via ContentDocumentLink. The ATS data is handled as a separate export workflow from the core chatbot data and imported after the main Contact migration to avoid schema conflicts.

Serviceform live chat session logs (visitor info, agent assignment, resolution status) migrate as Freshsales Tasks with TaskSubtype=Call or a custom activity type. Session metadata (wait time, resolution time) is stored in custom Task fields. Agent assignment resolves via the User email match established during the Team Members mapping phase.

Serviceform integration connections to third-party tools (CRM, email, analytics) are listed and preserved as an integration inventory document. We do not migrate integration credentials or rebuild connections automatically. The document lists each active integration with its configuration parameters so your admin can re-establish them in Freshsales or the Freshworks ecosystem post-migration.