Migrate from AgentLocator to Salesforce Sales Cloud

AgentLocator Lead maps directly to Salesforce Contact when the lead represents a known buyer or seller. Salesforce requires an AccountId for most Contact records — leads without a primary brokerage association are attached to a default 'Unassigned' Account or flagged for owner assignment.

AgentLocator Lead also maps to Salesforce Lead for prospects not yet converted. The split decision is based on AgentLocator's lead status: 'Active Buyer' or 'Active Seller' routes to Contact; early-stage leads route to Salesforce Lead for further qualification in Salesforce's standard model.

AgentLocator stores agent and brokerage information as contact properties or company records. These map to Salesforce Account — agent name becomes Account Name for the brokerage entity, and individual agents become Salesforce Contacts with an AccountId pointing to their brokerage Account.

AgentLocator pipeline stages (Active, Pending, Sold, Expired, Withdrawn) map to Salesforce Opportunity StageName pick-list values. Each stage requires value-by-value mapping, and probability percentages and forecast category are re-applied from Salesforce's stage configuration after migration. Salesforce validation rules reject records with stage values not present in the active Sales Process, so custom stages must be pre-created in Salesforce before the migration loads any Opportunity records.

AgentLocator saved searches store MLS listing criteria including price range, neighborhood, bedroom count, and other filters with no native Salesforce equivalent. FlitStack creates a Property_Search__c custom object with fields matching AgentLocator's search criteria, including Price_Range__c, Neighborhood__c, and Min_Bedrooms__c, with a lookup field to the Contact who owns each saved search. The custom object and all fields must be created in Salesforce before the migration loads any saved search records.

AgentLocator's native N:N relationship linking a Lead to a specific property listing requires reconstruction in Salesforce using a junction object (Lead_Property_Interest__j). This junction object contains lookups to the Contact (representing the buyer or seller) and a Property__c custom object (representing the listed property). Without this junction object, the many-to-many relationship between contacts and their property interests cannot be preserved in Salesforce's relational model.

AgentLocator's built-in dialer call logs, email threads, and SMS exchanges map directly to Salesforce Task records. Each migrated Task receives a Type field value of 'Call', 'Email', or 'SMS' respectively, with the original timestamp, call duration, and owner information preserved from the AgentLocator activity log. The ActivityDate and OwnerId fields are populated to maintain the original activity chronology and attribution in Salesforce.

AgentLocator's drip campaigns and automated listing emails are automation constructs with no Salesforce CRM equivalent. They are not data — they are logic. FlitStack exports the campaign definition (stage sequence, timing, content references) as a rebuild specification for Salesforce Flow or a marketing automation platform.

Every AgentLocator custom property (e.g., 'Lead Source Channel', 'Referral Partner', 'Mortgage Status') requires a Salesforce custom field with the __c suffix. The field type is matched (pick-list to pick-list, text to text) during the mapping phase, and fields are pre-created in Salesforce before data loads.

AgentLocator owner IDs are matched to Salesforce Users by email address. Unmatched owners are flagged before migration — the team either creates Salesforce users first or assigns records to a fallback user. No Opportunity or Contact lands in Salesforce without a resolved OwnerId.

Files attached to AgentLocator leads or contacts are downloaded from AgentLocator's storage and re-uploaded to Salesforce Files using the ContentDocument and ContentVersion model. Salesforce enforces a 25MB per-file size limit, and files exceeding this threshold require chunking or alternative storage. Inline images embedded in notes are extracted, rehosted as separate ContentDocument records, and re-linked back to the original note body.

AgentLocator's real estate-specific lead status values such as 'Active Buyer', 'Active Seller', and other transaction-stage designations map to Salesforce's standard Lead Status pick-list where matching values exist. For AgentLocator statuses with no Salesforce equivalent, FlitStack creates a custom pick-list field called Lead_RealEstate_Status__c on the Lead object to preserve the original real estate categorization scheme and ensure no lead classification data is lost during migration.