Migrate from Clientify to HubSpot

Clientify contacts map directly to HubSpot contacts. All standard properties (name, email, phone, job title, address) transfer on a one-to-one basis. Clientify contact status values require value-mapping to HubSpot lifecycle_stage. Owner resolution happens by email match against HubSpot users before migration begins.

Clientify stores contact lifecycle as a status pick-list (Lead, Customer, etc.). HubSpot uses lifecycle_stage with values: subscriber, lead, MQL, SQL, customer, evangelist. We map Clientify statuses to the closest HubSpot lifecycle values and preserve the original status change dates as a custom datetime property.

Clientify companies map to HubSpot companies. Company name, domain, industry, employee count, and annual revenue transfer directly. HubSpot parent-child company hierarchies use a dedicated Parent Company field — Clientify company hierarchies map to this field with circular reference detection.

Clientify deals map to HubSpot deals. Deal name, amount, close date, owner, and stage transfer. Each Clientify deal pipeline maps to a HubSpot deal pipeline — if Clientify has one pipeline, we create one HubSpot pipeline with matching stage names. Multi-pipeline setups require one HubSpot pipeline per Clientify pipeline.

Clientify stage names map to HubSpot deal stage names per pipeline. Stage probability and forecast category re-applied based on HubSpot's stage defaults — these can be adjusted after migration. Stage-entered timestamps from Clientify are preserved as custom datetime fields for reporting continuity.

Clientify tasks map to HubSpot tasks. Subject, body, due date, completion status, and owner transfer. Original create and completion timestamps preserved. Tasks linked to contacts or deals carry their association to the migrated records using the foreign key resolution sequence.

Clientify activity records (calls, emails, meetings) map to HubSpot's engagement objects. Call dispositions and duration transfer as custom properties on the HubSpot call record. Meeting end times and attendee lists map to HubSpot Event objects. Original activity timestamps preserved; owner assignment resolved by email match.

Clientify notes map to HubSpot engagement notes. Note body and associated contact/deal links transfer. Rich-text formatting is preserved where Clientify's export format supports it. Notes attached to contacts carry the association to migrated contact IDs.

Clientify custom properties map to HubSpot custom properties. Text, number, date, pick-list, and checkbox types map to HubSpot equivalents. Pick-list values require value-by-value mapping where Clientify uses different labels. Custom properties on contacts, companies, and deals are created in HubSpot before data migration begins.

Clientify's native WhatsApp inbox and WhatsApp flow automations have no direct HubSpot equivalent. HubSpot does not include built-in WhatsApp functionality — WhatsApp Business API must be configured separately, and all flows must be rebuilt. Clientify flow definitions are exported as rebuild documentation (triggers, conditions, wait steps, branching logic, and action sequences) for your HubSpot admin.

Clientify owner assignments on contacts and deals resolve by email match to HubSpot users. Unmatched owners are flagged before migration — your team invites them to HubSpot or assigns records to a fallback owner. Owner history from Clientify is preserved as a custom property.

Clientify records with lead status split based on lifecycle: prospects without deal activity become HubSpot Leads; contacts with deal history or customer status become HubSpot Contacts. The split logic is configurable — your team decides the threshold for lead vs. contact classification.