Migrate from Serviceform to Salesforce Sales Cloud

Serviceform Leads map directly to Salesforce Lead. Core fields (name, email, phone, source, qualification status) migrate to Salesforce standard fields. Serviceform's lead score and qualification properties transfer to custom fields (sf_lead_score__c, sf_qualification_status__c) for scoring and routing. Any Serviceform Lead with a resolved Account in Salesforce becomes a Contact via the standard Convert workflow post-migration.

Serviceform conversation logs (visitor messages, bot responses, timestamps, channel) map to Salesforce Task records. Each message in a conversation thread becomes a Task with Status=Completed, Subject set to the conversation summary, and Description containing the full transcript text. The original Serviceform timestamp migrates as ActivityDate for timeline ordering. Channel metadata (website chat, email, SMS) stores in a custom field sf_conversation_channel__c.

Conversations initiated via email in Serviceform map to Salesforce EmailMessage records. The message body and attachments migrate to EmailMessage.Body and ContentDocument records respectively. The WhoId points to the linked Lead or Contact; the WhatId points to the related Account or Opportunity if one was resolved during import.

Serviceform live chat session logs (visitor info, agent assignment, resolution status) map to Salesforce Task records with TaskSubtype = Chat. Agent assignment resolves via email match to a Salesforce User. Resolution status and session duration migrate to custom fields sf_chat_resolution__c and sf_session_duration__c.

Serviceform form definitions (field configurations, field types, conditional logic) are exported as a schema specification document rather than a transferable form. Each form's submission data maps to Salesforce standard fields where the field name and type match, and to custom fields (sf_form_field__c) where it does not. Conditional visibility rules are documented in the form specification for rebuild in Salesforce Flow or Web-to-Lead form settings.

Form submission data (field values, submission timestamp, source form name) migrates to Salesforce Lead records or a custom FormSubmission__c object depending on whether the destination org uses a custom object for web form captures. Submission metadata (form name, UTM parameters, referrer URL) stores in custom fields on the target record.

Serviceform chatbot flows (nodes, intents, response rules, conversation trees) are exported as a structured JSON schema and a visual flow diagram. This is a documentation artifact, not deployable automation. We deliver the full chatbot architecture as a written specification with intent mappings and recommended Salesforce Flow equivalents for the customer's admin to rebuild.

Serviceform user accounts with roles and seat assignments map to Salesforce User records. We resolve by email match. Active Serviceform users without a matching Salesforce User enter a reconciliation queue for admin provisioning before record import proceeds.

Serviceform integration connections (CRM links, email provider references, analytics tool references) are exported as a configuration list identifying each active integration and its connection parameters. We do not re-establish integrations during migration; we deliver the list so the customer's admin can reconnect each tool in Salesforce manually using the documented endpoints.

Serviceform ATS module applicant records (resume, candidate profile, ranking data) are exported as a separate dataset. These map to Salesforce Contact records if the destination org uses the Contact object for recruitment tracking, or to a custom Applicant__c object if the org has a pre-existing applicant schema. Resume files migrate as ContentDocument records linked via ContentDocumentLink.

Serviceform aggregates conversation metrics (conversion rates, bot performance, engagement rates) at read time from the underlying conversation data. These are not independently stored records and cannot be migrated. We preserve the raw conversation logs so that Salesforce reporting can recalculate equivalent metrics post-migration.

Custom properties on Serviceform chatbot nodes (custom attributes, metadata fields) are exported with the chatbot flow JSON. These map to custom fields on the Salesforce record type or object that represents the chatbot's destination context. If no matching Salesforce object exists, we recommend creating a custom ConversationMetadata__c object to hold these attributes.