Migrate from AgentLocator to Nutshell

AgentLocator leads map 1:1 to Nutshell Leads. All standard lead fields (name, email, phone, status) transfer directly. Custom fields on the lead — including forced-registration property, home search preferences, and any broker-specific data — migrate to Nutshell custom fields on the Lead object.

AgentLocator leads that have converted to clients (based on lifecycle status or a closed-deal flag) are also created as Nutshell People records. The migration creates both records and links them via Nutshell's CRM association, preserving the relationship between a lead and their person entity.

AgentLocator company records transfer directly to Nutshell Company objects during migration. Standard fields including company name, website URL, physical address, and industry classification migrate without transformation. Parent-child organizational hierarchies present in AgentLocator — where a company has subsidiary relationships — map to Nutshell's native parent-company relationship field when those hierarchies are configured in the source account, preserving the corporate structure in the destination CRM.

AgentLocator transaction records representing property deals, commissions, or closed transactions map directly to Nutshell Deal objects. Each deal carries essential properties including the deal name, monetary value or commission amount, current status, expected close date, and assigned owner agent. AgentLocator pipeline stage names do not map automatically to Nutshell's deal status values — instead, a value-mapping table is generated during the discovery phase that pairs each AgentLocator stage label with its corresponding Nutshell deal status, ensuring accurate pipeline representation in the destination system.

AgentLocator pipeline definitions and their stage names require a value-by-value mapping to Nutshell's deal status pick-list. We generate the mapping table during discovery by exporting AgentLocator's pipeline configuration and matching each stage label to the nearest Nutshell deal status. Probability and forecast-category metadata are stored as Nutshell custom fields if needed for reporting continuity.

AgentLocator notes and call activity logs migrate to Nutshell Notes and Tasks. Timestamps and owner assignments are preserved. Email activity recorded in AgentLocator migrates as Nutshell Tasks with Type='Email' so they appear in activity timelines in the correct chronological order.

AgentLocator's tag-based audience segmentation system migrates directly to Nutshell's Tag object model. Tags attached to leads, person records, and companies transfer without modification, maintaining the original tagging taxonomy. Multi-value tag lists stored as comma-separated string values in AgentLocator are parsed and exploded into individual Nutshell tag records, each linked to its parent entity — this ensures tags function as discrete filters and segmentation criteria in Nutshell's list views and reporting.

AgentLocator saved searches and lead filters have no native equivalent in Nutshell. We export the full search criteria for each saved search and store it as a long-text custom field on the associated Lead or Person record in Nutshell, so the original filter definition is preserved for manual reference and rebuild.

AgentLocator's forced-registration tracking — which records whether a lead has been required to register on the agent's website — has no native Nutshell equivalent. We create a custom yes/no field (Registration_Required__c) on the Lead object in Nutshell and populate it from the corresponding AgentLocator lead property. This field is critical for real estate teams that use registration status as a lead-quality signal.

AgentLocator's HomeLocator property-search history attached to leads — including saved listings, search criteria, and last-viewed properties — has no Nutshell equivalent. We store the full JSON payload of each lead's search history as a long-text custom field (HomeLocator_Search_History__c) on the Nutshell Lead. Rebuilding IDX associations in Nutshell requires a separate real estate integration (e.g., Realtor.com or ShowingTime plugin).

AgentLocator owner identifiers are resolved to Nutshell user accounts through email address matching. Before migration, FlitStack AI generates a comprehensive owner-resolution report that maps each AgentLocator owner to their corresponding Nutshell user by email. All migrated records receive a valid OwnerId assignment at load time. Owner records that cannot be matched are flagged in the pre-migration report — your team either creates new Nutshell user accounts for those agents or approves assignment to a designated fallback owner, ensuring no record enters Nutshell without a valid owner reference.

AgentLocator's internal record identifiers are preserved by storing them in a custom field (Source_System_ID__c) on every Nutshell record across Leads, People, Companies, and Deals. This source system ID field enables three critical migration functions: delta-run de-duplication on subsequent sync operations, full audit traceability linking each destination record back to its original AgentLocator source, and cross-reference lookup capability for support cases opened during the post-migration validation window.