Migrate from AgentLocator to HubSpot

AgentLocator stores leads and past clients as contacts. All migrate as HubSpot contacts with a custom lifecycle_stage property capturing the AgentLocator lead tier (buyer lead, seller lead, past client). Forced-registration flag maps to a boolean contact property so original lead-source attribution is preserved in HubSpot.

AgentLocator's property object (address, listing price, MLS number, property type, status, bedrooms/bathrooms) has no native HubSpot equivalent. All fields migrate as custom contact properties. For high-volume property portfolios, a separate HubSpot custom object is recommended — we include this option in the migration plan.

AgentLocator deals represent real estate transactions linked to contacts. They map to HubSpot opportunities with sale type, transaction price, and agent commission preserved as custom opportunity fields. The deal pipeline stage maps to HubSpot deal stage, and pipeline-specific attributes are carried forward for reporting continuity.

AgentLocator pipeline stages such as Active Lead, Under Contract, and Closed are mapped value-by-value to HubSpot deal stages. Stage order and entered-timestamp are preserved as HubSpot custom datetime fields to maintain reporting continuity throughout the migration.

AgentLocator tags migrate directly to HubSpot tags with exact label matching preserved. This ensures that segmentation, filtering, and list-building logic dependent on AgentLocator tags functions identically in HubSpot from day one of go-live.

AgentLocator notes attached to contacts and deals migrate as HubSpot notes with original create date, author, and full body text intact. Attachments included in AgentLocator notes are downloaded and re-uploaded to HubSpot Files to preserve all associated documentation.

AgentLocator agents and team members are matched to HubSpot users by email address. Unmatched agents are flagged before migration runs so your team can create HubSpot user accounts or assign records to a designated fallback owner before data loads proceed.

AgentLocator drip campaigns store a list of action steps per contact. These migrate as a custom text property (Campaign_Steps__c) preserving the sequence of actions. Actual workflow execution must be rebuilt in HubSpot's workflow builder using the exported campaign definitions as a reference.

AgentLocator built-in dialer call records map to HubSpot call activities (Tasks with Type=Call). Call duration, outcome, timestamp, and originating agent are all preserved so your complete communication history transfers to HubSpot without any loss of detail.

AgentLocator mass email and SMS logs attach to contacts as activities and migrate as HubSpot email activities with full content, send timestamp, and contact association preserved. SMS threads migrate as HubSpot engagement notes maintaining complete thread continuity for historical reference.

Any AgentLocator custom field beyond standard contact, property, and deal fields migrates as a HubSpot custom property on the matching object. Field type (text, number, date, picklist) is preserved throughout the migration. Picklist values are mapped value-by-value where the source picklist options differ from HubSpot defaults.

AgentLocator saved property searches store criteria that buyers use to track listings of interest. These migrate as a custom text property on the contact record capturing the full search criteria string. HubSpot lists and workflows can then reference this property for segmentation and automated follow-up triggers.