Migrate from REDA to HubSpot

REDA stores contacts using the standard Salesforce Contact object. Direct map to HubSpot Contact preserves first name, last name, email, phone, and job title. Owner resolved by email match against HubSpot users. Original Salesforce Contact IDs stored in a custom HubSpot field for traceability.

REDA accounts map directly to HubSpot companies. Account Name becomes Company Name; Industry pick-list values map via value-by-value mapping where HubSpot has matching options, defaulting to 'Other' where no match exists. Parent accounts map using HubSpot's parent company field, preserving hierarchical relationships. Additional standard fields such as website, phone, billing address, and annual revenue also transfer as direct mappings, while any custom account fields require pre-created HubSpot properties before migration.

REDA's primary property record — a custom Salesforce object — transforms into a HubSpot deal. Property name maps to deal name; property value or assessed value maps to deal amount; property status (Active, Leased, Sold) maps to a deal stage via value mapping. One property = one deal by default.

REDA unit records — sub-records of a property — split across multiple HubSpot records. Units with active tenants become separate deals linked to the parent property deal. Vacant units surface as HubSpot custom properties (unit_number, sq_ft, lease_status) on the parent property deal rather than standalone records.

REDA tenant records represent individuals associated with a property. Each tenant maps to a HubSpot contact. The property link (Tenant__c to Property__c) translates to a deal association in HubSpot. Multiple tenants for one property create multiple contacts, all associated to the same deal.

Property owners in REDA map to HubSpot contacts with a custom property Owner_Type__c set to 'Property Owner'. Owner contact details (name, email, phone) migrate as standard contact fields. Owner records that are also Salesforce users are matched by email to HubSpot users for deal ownership assignment.

REDA lease records — containing lease start date, end date, monthly rent, and security deposit — migrate as custom properties on the HubSpot deal representing the property. Lease status (Active, Expired, Month-to-Month) maps via value mapping to HubSpot deal stage or a custom pick-list.

Salesforce tasks and events linked to contacts or property records migrate as HubSpot engagements. Call tasks map to HubSpot calls; email tasks map to HubSpot emails; events map to HubSpot meetings. Original timestamps and owner assignments are preserved. Salesforce Note attachments migrate as HubSpot file attachments.

REDA property custom fields (Property__c.Zoning__c, Property__c.Year_Built__c, Property__c.Square_Footage__c) require HubSpot custom deal properties to be created before migration. Numeric and date fields map directly; pick-list fields require value-by-value mapping. FlitStack creates the custom HubSpot properties as part of the migration plan.

REDA allows N:N associations between contacts and accounts via AccountContactRelation. HubSpot supports a primary company on contacts plus secondary company associations. The primary (most-recently-modified) association migrates as the primary company; additional associations migrate as secondary company links in HubSpot. Secondary links are recorded in a custom multi-company field, allowing admins to review and reassign as needed after migration. This preserves the relationship graph while aligning with HubSpot's contact-company model.

REDA property records often have a Property_Manager__c field linking to a Salesforce user. This resolves by email match to a HubSpot user and becomes the deal owner in HubSpot. Unmatched managers are flagged before migration so your team can assign fallback owners or invite them to HubSpot.

REDA stores files (lease PDFs, property photos, tenant documents) as Salesforce Files (ContentDocument). These are downloaded and re-uploaded to HubSpot Files. Salesforce file size limits (25MB per file) apply; larger files are split or linked via URL reference where HubSpot supports external file links.