Migrate from Serviceform to Pipedrive

Serviceform Lead records (name, email, phone, source, qualification status, lead score) map directly to Pipedrive Person. We use email as the deduplication key and create the Person record before linking any conversation history or activity data. Custom properties on leads migrate as Pipedrive custom fields on the Person object.

Serviceform conversation transcripts map to Pipedrive Activity records. Visitor messages and bot responses become a Note attached to the Person record, with the original timestamp preserved for timeline ordering. We flag whether the conversation was initiated by the bot or escalated to a live agent based on Serviceform's session metadata. Full transcript migration is scoped separately from summary migration due to volume impact on the overall data set.

Serviceform Form submissions create or update Person records in Pipedrive. Each form field maps to a custom field on Person (or Organization if the field captures company data). Conditional logic on forms does not migrate; we document the original branching rules during discovery and provide a rebuild specification for Pipedrive Web Forms or a third-party form tool.

Serviceform chatbot flows (nodes, intents, response rules, and conditional branching) are not migratable as automation code. We export the flow structure as a JSON specification document and provide a mapping to Pipedrive workflow triggers. The customer's admin rebuilds chatbot flows in Pipedrive's LeadBooster or a dedicated chatbot platform. We preserve the flow names and node labels so the rebuild is not starting from scratch.

Serviceform user accounts with roles and seat assignments map to Pipedrive User records by email match. We resolve owner assignments on Leads and conversation assignments during migration. Any Serviceform user without a matching Pipedrive User is flagged in the reconciliation report for the customer's admin to provision before the migration phase.

Serviceform live chat session logs (visitor info, agent assignment, resolution status) map to Pipedrive Activity records attached to the Person. Session resolution status (resolved, pending, escalated) migrates as a custom picklist field on the activity. We use the session start timestamp as the ActivityDate to preserve the timeline sequence.

Serviceform ATS applicant records (resume, candidate profile, ranking data) are separate from the main chatbot data set and map to Pipedrive Person records with a custom field flagging the record source as ATS. Resume files are stored as Pipedrive attachments on the Person record. We treat ATS data as a distinct migration phase because it may require coordination with an HR system if the customer also uses a separate ATS in the destination stack.

Serviceform integration connections (CRM, email, analytics) are exported as a configuration inventory list during discovery. We do not re-establish integrations; we document what was connected, the integration type, and the recommended Pipedrive equivalent or the native Pipedrive integration name so the customer's admin can reconfigure after migration.

Serviceform lead qualification scores are stored as a custom property on the Lead record. We preserve this score in a Pipedrive Person custom field (numeric or rating scale depending on the source format) so that sales reps see qualification context at a glance. The scoring model itself requires manual review because Serviceform's scoring algorithm may not map directly to Pipedrive's deal probability model.

If the customer uses Pipedrive's LeadBooster Web Forms as the replacement for Serviceform forms, we document the original form field schemas and conditional logic so that form rebuilding is a guided specification rather than a reverse-engineering exercise. The form data itself migrates as Person custom fields before the new forms are deployed.