Migrate from Wise Agent to HubSpot

Wise Agent contacts map directly to HubSpot contacts. The contact's primary email, phone, address, and name fields transfer as HubSpot native properties. Owner resolution happens by email match against HubSpot user accounts — unmatched owners are flagged before migration commits.

Wise Agent company records (typically brokerage or franchise names) map to HubSpot companies. Company domain, name, phone, and address fields migrate as HubSpot company properties. Multiple contacts per company collapse to the HubSpot association model where one contact is primary and others link via company associations.

Wise Agent transactions are the core real-estate object and map to HubSpot deals. Property address fields (street, city, state, zip) are created as custom deal properties since HubSpot deals do not have native address fields. Transaction checklists, status, and agent assignments migrate as deal custom properties and deal-pipeline stage values.

Wise Agent transaction statuses (Active, Under Contract, Closed, Cancelled) map to HubSpot deal stages. We apply a default stage-probability mapping (Active at 20%, Under Contract at 60%, Closed at 100%, Cancelled at 0%) aligned with HubSpot's probability settings. Your team customizes stage names and probability percentages in HubSpot before the full migration runs to match your specific pipeline workflow.

Wise Agent labels (Buyer, Seller, Hot Lead, etc.) attach N-to-N across contacts. We consolidate all labels into a custom HubSpot multi-select property (e.g., wa_labels) on the contact record. This preserves the full label history without requiring a separate tag object.

Wise Agent task reminders and to-do items map directly to HubSpot tasks. Original due dates, task owners (resolved by email match), priority levels, and completion status transfer. Open tasks migrate as open HubSpot tasks with their due dates; completed tasks migrate with their completion timestamp preserved for historical record completeness.

Email history logged against a Wise Agent contact transfers to HubSpot's email activity on the contact record. Subject line, body preview, and timestamp migrate. Full email body content is preserved; inline images are downloaded and rehosted in HubSpot's file storage.

Wise Agent notes attached to contacts or transactions migrate as HubSpot notes. Original create timestamp and author (resolved by email) transfer. Rich-text formatting — including bold, italic, bullet points, and hyperlinks — is preserved where possible; plain-text fallback applied for unsupported formatting to ensure note legibility in HubSpot.

Wise Agent calendar events (showings, open house appointments) migrate as HubSpot meetings. Original start and end times, location (property address), attendees, and meeting description transfer. Owner attribution resolves by email match against HubSpot users. Recurring event patterns are noted for manual rebuild in HubSpot's meeting tools if needed.

Wise Agent drip campaigns (automated email/text sequences with enrollment triggers) have no HubSpot equivalent that preserves the original logic. We export campaign definitions as a structured document your HubSpot admin can use to rebuild sequences in HubSpot's workflow builder. This is a manual-rebuild item, not an automated migration.

Wise Agent text-message history (SMS logs) migrates as HubSpot calls with Type='SMS' on the contact record. Message content appears in the call notes. This preserves the communication record but does not recreate HubSpot's SMS add-on functionality, which requires separate configuration.

Wise Agent custom fields on contacts (beyond name, email, phone) are created as HubSpot custom properties before migration. Field type is mapped: text → string, number → number, date → date, dropdown → enumeration. Custom property names use HubSpot's snake_case naming convention.

Wise Agent agent/user accounts resolve by email match against HubSpot users. Unmatched agents are flagged with their associated record counts; your team either creates HubSpot user accounts for them or assigns their records to a designated fallback owner before migration commits. All records must have a resolved HubSpot owner to prevent orphaned data after migration.