Migrate from Real Estate CRM to HubSpot

Source contact records map directly to HubSpot Contact. HubSpot Contact stores firstname, lastname, email, phone, jobtitle, address, and lifecycle stage. Owner resolved by email match to HubSpot user. Contacts without a company link land as standalone contacts — a primary company can be associated later via HubSpot's association label.

Source company records map to HubSpot Company. HubSpot Company stores name, domain, industry, phone, address, and employee count. Parent-company hierarchies in the source map to HubSpot's parent company association via the hs_parent_company_id field. If a source company has multiple locations, each location can be represented as a separate HubSpot company linked to the parent.

Source deal records map to HubSpot Deal. HubSpot Deal stores dealname, amount, closedate, and dealstage. The dealstage pick-list values are mapped value-by-value from source stage names. Owner resolved by email match. A deal is associated to a primary contact via HubSpot's deal-to-contact association.

Source Property or Listing custom records map to HubSpot's Property custom object (available via HubSpot's real estate template). Property address, price, bedrooms, bathrooms, MLS number, and listing status migrate as HubSpot custom properties. The property record links to buyer/seller contacts via HubSpot associations.

Source transaction_type (Sale, Purchase, Lease, Rental) has no native HubSpot equivalent on the Deal object. FlitStack creates a deal-level custom pick-list property (transaction_type__c) in HubSpot and maps each source value by value. Admins define the pick-list options in HubSpot before the migration runs.

Commission split percentages stored as a custom text or number field on the source deal migrate to a HubSpot Deal custom property (commission_split__c). Teams using split-commission logic store it as a formatted string (e.g., '60/40') preserved verbatim. This field appears on the Deal record for quick reference during commission calculations.

Source showing records (date, time, property, outcome, buyer name) map to HubSpot Meetings with original start/end timestamps and owner preserved. The associated property reference migrates as a custom text field on the meeting (associated_property__c) since HubSpot Meetings do not natively link to the Property custom object.

Source call records migrate as HubSpot Calls with the original call date, duration, outcome, and owner preserved. Call disposition values (Connected, Left Voicemail, No Answer) are mapped to HubSpot's call outcome pick-list where possible, or stored in a custom field for custom disposition schemes.

Source email records migrate as HubSpot Email engagements. The email subject, body, timestamp, and owner are preserved. Attachments are re-uploaded to HubSpot's file storage. If the source email body uses HTML formatting, it is preserved as-is. This ensures that all communication history, including formatted content, remains intact for future reference and reporting.

Source notes migrate as HubSpot Notes attached to the relevant Contact, Company, Deal, or Property record. The original create timestamp and owner are preserved. Rich-text formatting in source notes is retained in HubSpot Notes. This allows teams to maintain detailed conversation context, agent comments, and client feedback across all records.

Source links between contacts and companies map to HubSpot's native Contact-to-Company association. HubSpot supports one primary company per contact plus additional associated companies. If the source has multiple primary companies per contact, the most-recently-modified company becomes the primary in HubSpot.

Source deal-contact links with role designations (Buyer, Seller, Agent, Co-Agent) map to HubSpot Deal-to-Contact associations. HubSpot's association labels (Buyer, Seller, Other) are used where they match source role names; custom role labels are preserved in a custom text field on the association.

Source file attachments on contacts, companies, deals, or properties are re-uploaded to HubSpot Files. Each file is attached to the corresponding HubSpot record. HubSpot's 25MB per-file limit is enforced; files exceeding this are flagged for manual re-upload. Original filenames are preserved.

Source user and owner records are matched to HubSpot users by email address. Unmatched owners are flagged before migration — teams either invite them to HubSpot or assign their records to a fallback HubSpot user. This ensures every migrated record lands with a valid HubSpot owner.

Source workflows, drip sequences, and auto-follow-up rules are not transferred. FlitStack exports workflow definitions as a structured JSON document so your HubSpot admin can rebuild automation logic in HubSpot's workflow tool, lists engine, and sequence tool. Sequence enrollments and workflow enrollment history do not carry over.