Migrate from AgentLocator to Twenty CRM

AgentLocator contacts map to Twenty's People object. Email serves as the unique identifier for import matching. First name, last name, phone, and job title transfer directly. AgentLocator's lifecycle tags (Lead, Active, Client) map to a custom pick-list field in Twenty since People has no native lifecycle stage.

AgentLocator company records map to Twenty's Companies object. Domain field in AgentLocator maps to the domain field in Twenty for company matching. Industry, address, and employee count fields transfer as-is. Parent-company hierarchies in AgentLocator become ParentId references in Twenty's Companies object.

AgentLocator supports N:N contact-to-company associations, allowing a single contact to link to multiple organizations simultaneously. Since Twenty People records have a single primary companyId, we migrate the most recently associated company as primary and surface remaining associations as a custom multi-select field or linked records for reference. We can alternatively create a custom junction object to maintain the full association graph if granular visibility into multi-company relationships is required for your workflow. Association timestamps are preserved in the migration documentation so your team can reconstruct relationship history in Twenty if needed.

AgentLocator deals map to Twenty Opportunities. Pipeline stage names (New Lead, Contacted, Showing, Offer Made, Closed Won, Closed Lost) map to Twenty's stage pick-list values. Deal amount, close date, and owner ID transfer directly. The deal name becomes Opportunity name.

AgentLocator listings (property addresses, MLS numbers, status) do not have a direct Twenty equivalent. We create a Property custom object in Twenty with fields for address, MLS number, listing status, and price. Listings link to Companies (seller) and People (buyer/agent) via relation fields.

AgentLocator tasks and follow-up reminders map to Twenty's Tasks object. Due date, assignee, status, and linked contact/company transfer directly. Task subject and body/notes map to Twenty's Task title and body fields, preserving all follow-up context. Any priority levels or recurrence patterns included in AgentLocator data are captured as custom fields where available, ensuring the complete scope of each task transfers over.

AgentLocator notes on contacts, companies, and deals map to Twenty's Notes object. Notes are linked to the respective People or Companies record via the noteTargetId and noteTargetObject metadata fields, maintaining the original relationship context. Creation timestamps and author attribution are preserved exactly as they appear in AgentLocator, so your team retains full conversation history and audit trails after migration.

AgentLocator tracks lead source (Website, Referral, Zillow, Realtor.com) on contacts. Since Twenty has no native campaign membership model, we create a leadSource__c pick-list field on People and migrate values directly. Campaign names and UTM parameters are preserved as text fields for reference, and we can optionally create a custom Campaign object to maintain the full campaign hierarchy if your team needs detailed attribution tracking.

AgentLocator tags on contacts (e.g., 'Hot Lead', 'Investor', 'Past Client') transfer as a multi-select text field or as Twenty tags if available. Tag groups map to separate custom fields for categorical filtering in Twenty views. For teams requiring advanced tagging workflows, we can implement Twenty's native tags feature if available in your plan to provide additional flexibility.

AgentLocator agent records map to Twenty WorkspaceMembers. We resolve by email match—AgentLocator owner email is matched against Twenty user email. Unmatched owners are flagged, and records are assigned to a fallback owner until accounts are provisioned. This mapping preserves team hierarchies and ownership assignments throughout the migration.

AgentLocator captures website leads via forced registration forms. Lead name, email, phone, and saved search criteria transfer to Twenty People. The form source (which landing page) maps to the custom leadSource field. Saved search criteria are stored as a text note for reference. All lead capture metadata is preserved for downstream follow-up workflows.

AgentLocator logs SMS and email activity on contacts. Since Twenty's timeline supports activity logging via API, we create timeline entries with type, timestamp, content, and direction (sent/received). Original communication content is preserved for audit purposes, and attachment references are documented for manual re-upload if needed. This ensures a complete activity history is available in Twenty for compliance and follow-up tracking.