Migrate from HaystackCRM to Twenty CRM

HaystackCRM Contact records map to Twenty CRM Person. Standard fields (first name, last name, email, phone, address) migrate directly. The source Contact's linked Company foreign key is resolved against pre-imported Company records to set the Person's Company relationship in Twenty. A custom text field haystack_contact_id__c preserves the original HaystackCRM record ID for audit and reconciliation.

HaystackCRM Company records map directly to Twenty CRM Company. Domain, address, phone, and industry fields migrate 1:1. We import Companies before Contacts to satisfy the lookup dependency. Company is the first object in the import sequence so that every subsequent Contact and Opportunity has a valid parent reference.

HaystackCRM Opportunities map to Twenty CRM Opportunity with dollar value, pipeline stage, status, and temperature priority preserved. Stage names are mapped to the closest Twenty pipeline stage. The Opportunity's linked Company and primary Contact migrate as Opportunity relationships after the Company and Person records are established. We validate that stage names in HaystackCRM map to valid Twenty pipeline values before migration.

HaystackCRM Tasks linked to a Contact or Opportunity migrate to Twenty CRM Task. We preserve the parent linkage by resolving the source Contact and Opportunity IDs against the imported Person and Opportunity records. Task status, priority, and due date migrate directly. Tasks without a resolvable parent are imported as orphaned records with a flag for manual re-association.

HaystackCRM calendar Events migrate to Twenty CRM Event as discrete date-bound records. Start time, end time, location, and title transfer directly. Calendar sync links (Google Calendar, iOS Calendar) cannot be reconstructed in Twenty CRM and must be rebuilt manually in the Twenty workspace settings. We document the original calendar link configuration in the pre-migration scope document.

HaystackCRM Quotes have no native equivalent in Twenty CRM's current feature set. We export Quote line items, pricing, and any generated PDF links as records in a dedicated Quote custom object that we create in Twenty before migration. PDF attachments migrate as file records linked to the related Opportunity. Customers who rely on in-platform quoting workflows should evaluate Twenty-compatible quoting tools post-migration.

HaystackCRM Item and Catalog entries migrate to Twenty CRM as Product records if the destination workspace has the products feature enabled. Product name, SKU, pricing, and description migrate directly. Line-item associations with Opportunities are reconstructed during the Opportunity import phase by resolving product references at migration time.

HaystackCRM flat tags map to Twenty CRM Labels. Tags are exported as string values from the CSV and mapped to the Label field on Person, Company, and Opportunity. Haystack's flat taxonomy has no hierarchy, so no parent-child restructuring is needed. Records with multiple tags are handled as multi-value label assignments per Twenty's label support on each object.

HaystackCRM Teams with role-based grouping map to Twenty Workspace Members. We export team membership and role names, then create a Workspace Member record for each unique owner referenced on Contacts, Companies, and Opportunities. Role granularity differs between platforms; Haystack territory and quota assignments do not have direct Twenty equivalents and are documented for manual reassignment in the new workspace.

HaystackCRM file attachments stored via Dropbox, iCloud, or OneDrive export as URL references. We export the attachment links and verify cloud storage connectivity before migration. Attachments cannot be downloaded and re-uploaded automatically without direct cloud credentials; we document the link inventory and advise customers to re-link or re-upload critical files in Twenty CRM post-migration.

HaystackCRM Users assigned as record Owners (Contacts, Companies, Opportunities, Tasks) export by email and name. We create a Workspace Member record in Twenty for each distinct Owner email before importing data records. Any Haystack Owner without a corresponding email address goes to a reconciliation queue for manual workspace member creation. Record Owner assignment migrates after Workspace Members are provisioned and validated.

HaystackCRM dashboard metrics are computed dynamically from live data and are not persistent records. We do not migrate dashboard snapshots or metric history. The dashboard should be rebuilt in Twenty CRM once data is loaded, using Twenty's built-in analytics and any custom views the team requires.