Migrate from Realvolve to HubSpot

Realvolve People map to HubSpot Contacts directly. HubSpot requires a primary Company association — for contacts without a primary company in Realvolve, we assign a default 'Unassigned' company or link based on your specified rule. All contact properties migrate as HubSpot custom properties if no native equivalent exists.

Realvolve Companies map to HubSpot Companies directly. HubSpot company hierarchies (parent/child) use the Parent Company field — we map Realvolve's parent-company relationship where present. Multi-contact companies in Realvolve map cleanly to HubSpot's one-company-per-contact model with secondary associations. Companies without any contacts are preserved as standalone company records.

Realvolve Transactions are the core revenue object and map to HubSpot Deals. Realvolve's transaction stages (Active, Pending, Closed) map to HubSpot pipeline stages per your specified stage mapping. Each Realvolve transaction-party association (Buyer Agent, Seller Agent, Title, Lender) maps to HubSpot Deal associations or a custom junction object.

Realvolve transaction stages (e.g., Active, Under Contract, Inspection, Appraisal, Closing, Closed, Cancelled) map value-by-value to HubSpot Deal Stage values. We preserve stage-entry timestamps as custom datetime properties on the HubSpot Deal so reporting can reflect original transaction timeline. Stage transition history is reconstructed from Realvolve's audit trail if available.

Realvolve workflows have no direct HubSpot equivalent. We export every workflow definition as a structured JSON document listing triggers, conditions, actions, and pause-wait configurations. This serves as a rebuild reference for HubSpot Automation or Breeze. Workflow packages (Transaction Coordination, Listing Management, Sphere of Influence) are exported separately.

Realvolve Tasks map to HubSpot Tasks with subject, body, due date, owner, and completion status preserved. Completed tasks migrate with original completion timestamps. Tasks linked to specific contacts, companies, or transactions carry their association links into HubSpot. Recurring task patterns are noted for workflow rebuilding in HubSpot.

Realvolve File Manager documents migrate to HubSpot Files. Each file is re-uploaded to HubSpot's file storage and associated to the relevant Contact, Company, or Deal record. HubSpot's file size limit of 30MB per file applies — files exceeding this are flagged for manual handling.

Realvolve logged emails, SMS messages, and calls migrate as HubSpot Engagements. Email engagements map to HubSpot's email timeline on the Contact record. Call logs migrate as HubSpot Call engagements with disposition and duration. Original timestamps and owner assignments are preserved.

Realvolve custom fields on People objects that have no native HubSpot equivalent (e.g., License Number, Transaction Role, Sphere Category) are created as HubSpot custom properties on the Contact object. Property type is inferred from Realvolve's field type — pick-list, text, date, and number fields map to their HubSpot equivalents.

Realvolve transaction custom fields (e.g., MLS Number, Property Type, Commission Split, Closing Date Override) map to HubSpot custom properties on the Deal object. These must be pre-created in HubSpot before the migration run so field IDs can be mapped correctly.

Realvolve users are resolved by email match against HubSpot users. Unmatched Realvolve users are flagged before migration — your team either creates HubSpot user accounts first or assigns their records to a fallback owner. No record lands in HubSpot without a valid owner.

Realvolve calendar events map to HubSpot Meetings with original start/end times, attendees, location, and body preserved. Meetings linked to Realvolve contacts carry their association into HubSpot so the contact timeline shows the full meeting history. Recurring meeting series are noted as rebuild candidates for HubSpot's sequence or automation tools.

Realvolve Notes map to HubSpot Notes with body text, associated record, and original create timestamp. Rich-text formatting is preserved where possible. Notes without an associated record are attached to the closest related contact or company. Internal note flags are translated to HubSpot's note visibility settings.

Realvolve contact categories (ABCD classification system mentioned in help docs) and tags map to HubSpot Lists or a custom multi-select property depending on usage pattern. Static lists migrate as HubSpot static lists; dynamic rule-based categories are noted as rebuild candidates for HubSpot's list filtering.