Migrate from Real Estate 7 to HubSpot

Real Estate 7 stores contacts in WordPress user tables and a custom CT Contact post type. HubSpot Contact receives firstname, lastname, email, phone, address, and custom properties directly. Owner resolution happens by email match against HubSpot users — unmatched owners flagged before migration.

Brokerage and agency records in Real Estate 7 map directly to HubSpot Company objects. The mapping preserves company name, domain, address, industry classification, and employee count. Parent-child company hierarchies present in Real Estate 7 are maintained through HubSpot's parent_company_id association field, ensuring organizational structure transfers intact.

Real Estate 7's CT Listing is a custom post type with price, beds, baths, sqft, MLS ID, property type, status, showing instructions, and HOA fee fields. HubSpot has no standard Property object — we create a Property__c custom object (Enterprise) and map every listing field. Address components compose into HubSpot's street, city, state, zip format.

Listing status values from Real Estate 7 map to a Property__c.Status__c pick-list in HubSpot. The 'Active' status maps directly to 'Active', 'Pending' maps to 'Under Contract', and 'Sold' maps to 'Closed'. Any custom or non-standard status values present in Real Estate 7 require individual value-by-value mapping during the planning phase before migration runs.

Real Estate 7 tracks which contacts are interested in which listings. HubSpot's standard Contact-Deal association doesn't cover property interests — we create a Property_Interest__c junction object linking Contact to Property__c with fields for interest type (buyer / seller / renter), status, and date.

Real Estate 7 calculates a 0–100 lead score based on engagement. We preserve this as Lead_Score__c on HubSpot Contact. HubSpot's native lead scoring is separate and must be rebuilt as a HubSpot Workflow or Breeze AI feature — the historical score value is preserved for reporting continuity.

Real Estate 7 lets agents create property alerts and assign them to leads. HubSpot has no direct alert object — we split these into HubSpot Lists (static lists per alert type) and Workflow enrollment triggers. Active alert subscriptions become Workflows that re-enroll contacts when matching properties are added.

Real Estate 7 task records (follow-ups, showing schedules, call logs) map to HubSpot Tasks. Original due dates, owners, and completion status preserved. Task subject and body translate directly. Tasks linked to Property__c records maintain the association via the Property_Interest__c junction or a custom task field.

Agent notes created in Real Estate 7 transfer to HubSpot as Engagement Notes attached to the relevant Contact or Property__c record. We preserve original creation timestamps and owner IDs from the WordPress system. Notes containing rich-text formatting retain their formatting during migration. Any notes associated with listings are linked to the corresponding Property__c record through a custom note association field to maintain context.

Real Estate 7 campaign definitions (email lists, trigger conditions, timing rules) do not have a HubSpot equivalent at the data layer. We export campaign names, associated contact lists, and send-history as a reference CSV for your HubSpot admin to rebuild using HubSpot Workflows and Campaigns.

Real Estate 7 stores files attached to listings and contacts (photos, PDFs, contracts) in the WordPress media library. We download all media, re-upload to HubSpot Files, and associate them to the corresponding Contact or Property__c record. File size limits apply — HubSpot supports up to 250MB per file.

Real Estate 7's Follow Up Boss integration syncs leads and activity data bidirectionally. After migration to HubSpot, the Follow Up Boss integration must be replaced with HubSpot's native lead management. Historical FUB activity (calls, texts, showings) is preserved as HubSpot Tasks and Notes.