Migrate from Wetroo to HubSpot

Direct map. Wetroo contact records map to HubSpot contacts with all standard properties transferred. The HubSpot contact record is the primary destination for Wetroo contact data, preserving original create dates and last-modified timestamps as HubSpot properties. All contact associations to companies and deals are carried over, ensuring linked records remain intact in the new environment.

Wetroo does not split contacts and leads into separate objects. All Wetroo lead records migrate to HubSpot contacts, with the original lead qualification status preserved as a HubSpot custom property (Lead_Status__c) since HubSpot uses lifecycle_stage rather than a binary lead/contact split.

Direct map. Wetroo company records map to HubSpot company records. Parent-child company hierarchies in Wetroo translate to HubSpot's parent company association using the parent_company_id field to populate the HubSpot parent company lookup. This mapping preserves corporate structure, allowing you to maintain reporting by subsidiary and roll up revenue across the organization.

Direct map. Wetroo deal records migrate to HubSpot deal records. Each Wetroo deal carries its associated pipeline and stage values, which map to corresponding HubSpot deal pipeline and stage configurations in the destination portal. Deal amounts, close dates, and owner assignments are also transferred, keeping the full sales context available in HubSpot for forecasting and reporting.

Wetroo pipelines map to HubSpot deal pipelines. We create a HubSpot pipeline for each unique Wetroo pipeline, preserving stage names and ordering. Stage probabilities and required-field configurations are applied based on Wetroo stage metadata where available. If a Wetroo pipeline references custom fields not yet present in HubSpot, those fields are flagged for creation before the pipeline goes live.

Stage names are mapped value-by-value from Wetroo to HubSpot. Each Wetroo stage label is matched to a HubSpot stage label in the corresponding pipeline. Unmapped stages are created as new HubSpot stages and flagged for your team's review before the migration run commits.

Wetroo owner records resolve to HubSpot users by email match. We query HubSpot users by email address; any Wetroo owner whose email does not correspond to an existing HubSpot user is flagged as an unresolved owner and mapped to a designated fallback owner for review before migration.

Wetroo custom properties on contacts, companies, and deals map to HubSpot custom properties. We create each custom property in HubSpot with the appropriate type (string, number, date, picklist) before loading data. Picklist-type custom properties require value-by-value mapping where Wetroo uses restricted picklist options.

Wetroo email logs, call records, and meeting records migrate as HubSpot engagements (email, call, meeting). Original timestamps, owners, and associated contact or deal links are preserved. Engagement type and direction (sent/received) map to HubSpot engagement metadata. Call disposition values are stored as custom engagement properties, enabling reporting on outcome categories without altering the native engagement schema.

Wetroo WhatsApp conversations have no native HubSpot equivalent. We migrate conversation summaries and timestamps as HubSpot engagement notes with a custom property (WhatsApp_Conversation__c) flagging the record. Full message threading is preserved in an attached JSON export for reference. Rebuild WhatsApp automation in HubSpot using the Conversations inbox.

Wetroo sequences and automation playbooks do not migrate to HubSpot. These are exported as a structured reference document mapping Wetroo trigger conditions, delay rules, and action sequences. Your HubSpot team uses this document to rebuild equivalent logic in HubSpot Sequences (Sales Hub) or Workflows (Operations Hub).

Wetroo file attachments associated with contacts, companies, or deals re-upload to HubSpot Files. Each file is linked to its parent record using HubSpot's file association model. Inline images in notes are extracted, rehosted as HubSpot-hosted assets, and relinked in the note body.