Migrate from Serviceform to HubSpot

Every Serviceform form submission creates a contact record. Standard fields (name, email, phone, company) map directly to HubSpot's Contact properties. Unique form-field data creates custom contact properties in HubSpot. Original submission timestamp preserved as a custom datetime property. Each custom property is created with the appropriate data type (text, number, picklist, date) based on the source field definition, and default values are set where applicable.

Serviceform chatbot conversations are visitor-level logs. Each conversation that produces a qualified lead maps to the resulting HubSpot Contact, with the conversation outcome (qualified, booked, unanswered) recorded as a custom property. Full conversation transcripts are stored as HubSpot engagement notes on the contact timeline.

When Serviceform captures company name (via form field or enrichment), it maps to a HubSpot Company record. The Company is then associated to the Contact via HubSpot's native association model. If no company data exists, the contact is created without a company association — FlitStack flags these for manual review.

Each Serviceform form field that doesn't match a HubSpot standard property (e.g., a custom lead source question or industry-specific dropdown) requires a custom HubSpot contact property. FlitStack creates these properties during migration, applying the correct data type (text, number, date, picklist) based on the source field definition.

Serviceform team members and assigned agents map to HubSpot users by email address. Unmatched agents are flagged before migration — the team either creates HubSpot users for them or assigns their contacts to an existing user as a fallback. Deactivated Serviceform users are preserved in a custom field for audit purposes.

Serviceform chatbot flows contain conditional logic, answer branches, and integration triggers that have no direct HubSpot equivalent. FlitStack exports the complete flow configuration as a structured JSON document. HubSpot's Workflow Builder or Sequences replicate the logic — the export serves as the rebuild specification.

Live chat sessions in Serviceform map to HubSpot engagement timeline entries (Notes) on the associated Contact record. The session timestamp, agent assigned, and a summary of the chat are preserved. Full transcript stored as a note attachment for reference by the sales team.

Serviceform records which form a contact submitted, which chatbot flow they engaged, and the UTM parameters present at submission. This metadata maps to HubSpot's original_source_bit, hs_analytics_source, and a custom property capturing the specific Serviceform form identifier for attribution analysis. The mapped fields enable channel-level performance reporting, allowing marketing to see which forms and chatbot flows generate high-value leads and to optimize future campaigns accordingly.

If the Serviceform ATS module was active, candidate records map to a HubSpot custom object (Enterprise tier) or as Contacts with a custom candidate_type property. Custom fields on candidates (resume URL, skills, status) require equivalent custom HubSpot properties. The ATS-to-HubSpot custom object mapping is scoped per implementation.

Serviceform integrations (WhatsApp, Zapier, email tools) have no direct HubSpot equivalent and cannot migrate. FlitStack documents each active integration with its trigger/action logic. The HubSpot App Marketplace or HubSpot's API is used to rebuild these connections in the new environment.