Migrate from Wetroo CRM to HubSpot

WhatsApp message threads have no native HubSpot object — conversation context is stored as custom properties

HubSpot's engagement model supports email, calls, meetings, and tasks natively. Wetroo's WhatsApp conversations (stored as message threads with direction, timestamp, and content per message) have no direct HubSpot equivalent. FlitStack loads these as HubSpot engagements of type 'email' with the message thread embedded as a custom multiline text property on the Contact or Deal. HubSpot admins should be aware that WhatsApp history will not appear in HubSpot's standard timeline view without a custom card or timeline extension — it is preserved as a data reference, not a native activity feed entry. This is a destination-side limitation, not a data loss event.

Wetroo automation rules do not export to HubSpot workflows — a rebuild reference document is the deliverable

HubSpot's workflow engine (Workflows in the Automation menu) does not import Wetroo's Automation 360 definitions. The automation logic — sequence triggers, task-creation rules, stage-change notifications, and WhatsApp drip cadences — must be rebuilt inside HubSpot's workflow builder or transferred to HubSpot Sequences. FlitStack exports Wetroo's automation definitions as a structured document (trigger conditions, actions, and timing rules) that your HubSpot admin can use as a rebuild checklist. The marketing contact flag and HubSpot's own automation logic will interact differently with HubSpot's enrollment triggers than they did in Wetroo, so plan a review of every critical automation before go-live.

HubSpot lifecycle stage must be assigned on import — Wetroo contacts have no equivalent concept

HubSpot uses lifecycle_stage as the primary prospect-to-customer property on every Contact record. Wetroo contacts have no corresponding lifecycle-stage field — the Wetroo model uses deal stage and task completion as the de-facto progress indicators. Without an explicit mapping rule, all migrated contacts land with a null lifecycle_stage, which disables HubSpot's reporting by lifecycle, triggers in workflows that depend on lifecycle enrollment, and may cause marketing automation to misfire. FlitStack applies a mapping rule during migration: contacts with a closed-won Wetroo deal receive lifecycle_stage 'customer'; all others receive 'lead'. You can override this mapping with a custom rule based on Wetroo lead status or deal stage before migration runs.

Wetroo's OBD call records require custom engagement property creation before migration

HubSpot's built-in call logging expects call records to be created via the HubSpot mobile app, the Sales Chrome Extension, or the calling integration. Wetroo's OBD (outbound dialer) call records — which include call duration, disposition, recording URL, and SIM metadata — do not match HubSpot's native call engagement schema directly. FlitStack stores these as HubSpot Engagements with call_type = 'outbound_call' and maps Wetroo's specific call fields (duration, disposition, recording) to HubSpot custom properties created on the Engagement object before the migration runs. The Engagement is then linked to the Contact via HubSpot's association API. This requires the Engagement object to have the custom properties pre-created in your HubSpot portal.

HubSpot's per-contact marketing billing does not apply to Wetroo-imported records — the billing model resets

HubSpot bills marketing features based on the number of contacts marked as 'marketing contacts'. Wetroo has no equivalent concept — all Wetroo contacts are treated uniformly for billing purposes. When contacts migrate to HubSpot, they land as standard CRM contacts with no marketing-contact flag set by default. HubSpot's marketing automation (email sends, workflow enrollments) will count these as contacts but the marketing-contact billing tier depends on your HubSpot plan and how many contacts receive marketing emails. FlitStack preserves Wetroo's lead_source and Facebook attribution data so your HubSpot admin can determine which contacts should be flagged as marketing contacts based on the original lead source after migration.