Migrate from AgentLocator to Pipedrive

AgentLocator leads map directly to Pipedrive People. First name, last name, email, phone, and source campaign tag migrate as Person fields and a custom tag field. Owner resolves by email match against Pipedrive users, ensuring each lead lands under the correct team member's account.

AgentLocator listing records — address, price, MLS ID, status, bedrooms, bathrooms — have no native Pipedrive equivalent. We create custom fields on the Deal object (Listing_Address__c, Listing_Price__c, Listing_Status__c, etc.) and attach each property record to the relevant buyer Deal for comprehensive transaction tracking.

AgentLocator's buyer-interest object links one lead to multiple listings and captures criteria (price range, neighborhoods, property type). Since Pipedrive Deals link to one Person at a time, we store the property list as a comma-separated custom field and attach full criteria as a Note on the Deal.

AgentLocator's brokerage or team name migrates as a Pipedrive Organization. This preserves the hierarchical relationship between agents and their brokerages. AgentLocator agents without a brokerage affiliation land as standalone People without an Organization link, maintaining their individual contact records.

AgentLocator lead source campaigns (Google Ads, Facebook Ads, Tag Marketing) are preserved as a text custom field on the Person record. Pipedrive's built-in campaign tracking is not equivalent — this field preserves attribution history and ensures marketing performance data carries over after migration.

AgentLocator stages (New Lead, Showing, Offer Made, Under Contract, Closing, Sold) map one-to-one to Pipedrive pipeline stages. Each stage name, probability, and order is recreated in Pipedrive's stage editor per pipeline, maintaining the same workflow progression that agents are familiar with.

AgentLocator calls, emails, meetings, and SMS threads migrate as Pipedrive Activities. Timestamps, duration (for calls), and the agent owner are preserved. Subject and body map to Activity subject and notes fields, keeping the full communication history intact within each deal record.

AgentLocator custom fields (HomeLocator preferences, AI BOT conversation count, forced-registration details) are recreated in Pipedrive using the same field name and type where supported. Pipedrive field types differ from AgentLocator in some cases — we document the type mapping per field for admin reference.

AgentLocator tags used to categorize leads (buyer, seller, investor, etc.) migrate as a custom text field on the Person. Pipedrive does not have a native tag object at Person level — this field preserves segmentation logic and allows teams to filter contacts by their original categorization after migration.

AgentLocator agent accounts are matched to Pipedrive users by email address. If an AgentLocator agent has no Pipedrive user account, their records are assigned to a fallback owner and flagged for review before migration commits, preventing orphaned records in the target system.

AgentLocator's direct MLS board connections are platform-specific integrations with no Pipedrive equivalent. We export listing IDs, last-synced timestamps, and feed credentials as a structured JSON reference file for your team to reconnect via a Pipedrive-compatible MLS add-on after migration completes.

AgentLocator drip campaigns, automated email sequences, and AI BOT conversation flows are tied to AgentLocator's proprietary automation engine. We export the campaign definitions (trigger conditions, message sequences, delay rules) as a readable spec so your Pipedrive admin can rebuild them in Pipedrive Automations.