Migrate from Agent Legend to Twenty CRM

Agent Legend Contact maps 1:1 to Twenty People. All standard contact fields (name, email, phone, address, job title) transfer directly. Owner assignment resolves by email match to a Twenty workspace member — unmatched owners are flagged before migration so the team can invite them or assign a fallback owner before records land.

Agent Legend Company maps to Twenty Company. Company name, domain, industry, employee count, and revenue fields transfer directly. Agent Legend parent-company hierarchies map to the Twenty Company relation field where available. Multiple company associations per contact are surfaced post-migration for manual linking.

Agent Legend Deals map to Twenty Opportunities. Deal name, amount, stage, and expected close date map to Opportunity fields. Deal stage values are mapped via value-mapping since Twenty's Opportunity stage pick-list is configurable. Deal owner resolves via email match to Twenty workspace member.

Agent Legend Campaign has no native equivalent in Twenty's standard object model. We create a Campaign custom object in Twenty during schema setup with fields for name, type, status, start date, and end date. Campaign metadata migrates as records in this custom object. This is the foundation for campaign-level reporting in Twenty.

Campaign membership links a Contact to a Campaign with a status field. Twenty has no built-in membership tracking. We create a CampaignMember junction object that links People records to Campaign custom object records using email as the unique identifier. This preserves the many-to-many relationship from Agent Legend.

Agent Legend's Lily AI lead score (integer 0–100) has no native equivalent in Twenty. We create a custom Number field called Lead_Score__c on the People object during schema setup. Lily scores populate during migration, and teams can use this field in Twenty's filter views, kanban grouping, and API exports. This preserves the prioritization signal built in Agent Legend.

Agent Legend logs outreach activities (email, SMS, call) on contact records with original timestamps and owners. We map these to Twenty Tasks with Task Type pick-list values (Email, Call, SMS) so the outreach history is searchable in Twenty. Each Task is linked to the People record via the relation field. Note that Twenty's activity tracking is manual by default — new outreach must be logged by users or via API.

Agent Legend notes on contacts and companies migrate to Twenty's Note object. We map the note body directly. File attachments are not included in Agent Legend's CSV export — we document which records had attachments so the team can re-upload them post-migration. Large attachment volumes may require a separate file transfer step via API.

Agent Legend custom fields on Contacts, Companies, Deals, or any custom object map to Twenty custom fields. We create matching custom fields in Twenty's data model before migration, matching field types (text, number, date, select, multi-select). Select and multi-select fields preserve the value list from Agent Legend. Teams should review custom field usage during scoping to decide which fields are worth migrating.

Agent Legend users and owners are matched to Twenty workspace members by email address. We run an email lookup against the Twenty workspace during migration. Unmatched owners are flagged in the migration report — the team either invites them to Twenty first or assigns their records to a fallback owner. No record lands without a valid Twenty owner assignment.

Agent Legend tags on contacts (e.g., 'Hot Lead', 'Investor', 'Past Client') have no native equivalent in Twenty. We map these to a custom select field (Contact_Tags__c) on the People object. Teams can consolidate overlapping tags or rename them during migration planning to reduce the pick-list size in Twenty.

Agent Legend pipelines group deals by stage. Twenty uses Opportunity stage values and kanban grouping to represent pipeline views. We map each Agent Legend pipeline to a set of Opportunity stage values in Twenty. Stage probability and order are preserved as custom fields if the team uses them for forecasting. Pipeline configuration is rebuilt in Twenty's kanban UI post-migration.