Migrate from PropertySimple to HubSpot

PropertySimple contact records map directly on a 1:1 basis to HubSpot contacts, preserving all record identifiers and field values. All standard fields including name, email, phone, and address transfer directly without transformation. HubSpot's lifecycle_stage property is set according to your specified default configuration, typically initialized as 'lead' unless the record carries purchase history evidence from PropertySimple that warrants a different stage designation.

PropertySimple contacts identified as having completed a transaction—whether through listing history or referral records—route to HubSpot contacts with lifecycle_stage explicitly set to 'Customer' status instead of the default lead stage. This routing ensures that established customer relationships are properly recognized in HubSpot's lifecycle model. The original source transaction flag from PropertySimple is preserved as a custom property on the HubSpot record for audit trail continuity and future reference purposes.

PropertySimple agent profiles are not CRM contacts — they represent the subscription seat. FlitStack matches agent email addresses to HubSpot user accounts and sets OwnerId on all migrated records accordingly. Unmatched agents are flagged and assigned to a fallback owner before migration commits.

PropertySimple company or brokerage records migrate directly to HubSpot companies, maintaining all organizational data integrity. Core fields including company name, domain, industry classification, and physical address transfer directly without transformation. Additionally, parent-brokerage relationships defined in PropertySimple map to HubSpot's parent-company hierarchy when your account configuration utilizes this organizational structure, preserving your corporate reporting relationships.

PropertySimple listings map to HubSpot deals. Listing address becomes Deal name (or a custom address field). Listing price becomes Deal amount. Property status in PropertySimple (active, pending, sold) requires a value-mapping to HubSpot pipeline stage names — FlitStack creates a dedicated real estate pipeline in HubSpot with stages matching your PropertySimple status values.

The PropertySimple agent linked to a listing resolves to a HubSpot user by email match, and that user becomes the Deal OwnerId. If a listing has a co-agent, both resolve to HubSpot users and the secondary agent is recorded in a custom Agent_Co_Owner__c field on the Deal.

PropertySimple's ZIP Code plan stores territory exclusivity as an agent or account-level flag. This has no native HubSpot equivalent — FlitStack creates a ZIP_Territory__c custom property on the Contact or Company object and writes the claimed ZIP code value so the association survives in HubSpot.

PropertySimple automated social posting campaigns and associated ad creative records have no direct equivalent functionality in HubSpot's native toolset. To support your team's rebuild efforts, FlitStack exports comprehensive reference data including campaign names, execution dates, and content themes as a structured CSV file. Your team can use this exported reference material to manually reconstruct equivalent social-media and advertising workflows within HubSpot's workflow editor and ad management tools.

PropertySimple engagement logs (calls logged against a contact, emails sent) map to HubSpot tasks with Type set to 'Call' or 'Email'. Original timestamps, owners, and parent-contact links are preserved. Notes attached to activities migrate as HubSpot engagement notes on the associated contact timeline.

PropertySimple tracks how a lead entered the system (social ad, referral, ZIP territory landing page). These values migrate as custom string properties on the HubSpot contact so attribution data is preserved even though PropertySimple's source-tracking attribution model differs from HubSpot's native UTM model.

PropertySimple custom fields defined on agent profiles—including team_name, license_number, and plan_type—migrate as custom properties on the corresponding HubSpot user record, or alternatively as contact-level properties based on your specified schema configuration plan. This flexibility ensures the data lands in the most useful location for your reporting and workflow needs. FlitStack automatically creates any missing HubSpot properties before the validation process runs, preventing schema-related migration failures.