Migrate from Sierra Interactive to Twenty CRM

Sierra's Lead object maps directly to Twenty's People object. All standard contact fields (name, email, phone, address) transfer as-is. Sierra-specific fields like lead source and tags become custom fields in Twenty's Data Model before import. Owner assignment resolves by email match to Twenty workspace members.

Sierra's Company object maps 1:1 to Twenty's Company object. Company name, website, address, and industry fields transfer as direct mappings. Sierra company phone and revenue fields map to custom number/text fields in Twenty. Parent-child company hierarchies preserve using the parentId relationship.

Sierra Deals map to Twenty Opportunities. Deal name becomes Opportunity name; deal value maps to Opportunity amount; pipeline stage names map via value_mapping to Twenty's stage pick-list. Close date transfers as-is. Pipeline assignment becomes a custom select field in Twenty since there is no native pipeline object.

Sierra notes on leads or companies migrate to Twenty Notes attached to the corresponding People or Company record. Original timestamps and author information (resolved by email) attach as metadata fields. Rich-text formatting in Sierra notes converts to plain text for Twenty's Note field.

Sierra tasks linked to leads or deals map to Twenty Tasks on the corresponding People or Opportunity record. Task subject, due date, completion status, and assigned user (via email match) all transfer. Task type (call, email, other) becomes a custom select field in Twenty since there is no native task-type classification.

Sierra Lead Ponds (grouped lead buckets) have no Twenty equivalent. Each unique Lead Pond name becomes a custom select field on the People object in Twenty's Data Model. The import script populates this field for each contact based on the source pond assignment. Admins recreate pond logic as filter views in Twenty.

Sierra saved searches stored per lead become a custom text field (Saved_Search_Criteria__c) on the People record in Twenty. The raw search criteria string transfers as-is. If the saved search has a name, that name becomes a custom select value for easier reporting. Teams rebuild active searches as Twenty views with matching filter conditions.

Sierra saved listings per lead have no Twenty equivalent. The listing MLS number, address, and save date migrate as custom text fields on the People record. If multiple listings are saved per lead, the most-recently-saved listing is marked as primary and others surface as additional text entries. Teams needing full listing history use a custom object in Twenty.

Sierra Action Plans (automated email, text, voicemail, and task sequences) do not migrate. They are exported as a structured JSON document that lists every sequence, trigger condition, and action step. This document serves as the specification for rebuilding equivalent logic in Twenty's workflow builder or an external sequencing tool like Lemlist or Saleshandy.

Sierra lead tags become a custom multi-select field (Lead_Tags__c) on the People object in Twenty. Tag values are enumerated from Sierra's tag list during the audit phase and mapped value-by-value. Multi-select allows a single contact to carry multiple tags. Admins rebuild tag-based routing in Twenty as workflow conditions or view filters.

Sierra users and deal owners map to Twenty workspace members. The mapping resolves by matching Sierra user email to Twenty member email. Any Sierra owner without a corresponding Twenty member is flagged before migration; those records assign to a fallback owner or land in an unassigned state pending team onboarding in Twenty.

Sierra's lead source field (e.g., website, referral, PPC) maps to a custom select field (Lead_Source__c) on the People object in Twenty. Each Sierra source value is enumerated and mapped to a corresponding Twenty pick-list option. If a source value has no match, it creates a new pick-list entry before migration.

Sierra file attachments on leads, companies, or deals migrate as Twenty attachments linked to the corresponding record. File size limits follow Twenty's standard attachment constraints. Inline images in notes are extracted, re-hosted, and the URLs updated in Twenty's note body.

Sierra's IDX website data, listing inventory, and site analytics are outside the CRM data model and do not migrate. These are separate systems. Teams migrating away from Sierra's IDX platform need to select a new website host and re-integrate MLS feed data independently of the CRM migration.