Migrate from Friday CRM to Twenty CRM

Friday CRM Company records map to Twenty CRM Organization. The Company name maps to Organization name, domain maps to the Organization website field, and address fields map to Organization address fields. We use Company name as the dedupe key during import and create Organization records before Contact records so that the relationship lookup is satisfied at insert time.

Friday CRM Contact records map to Twenty CRM Person. First name, last name, email, phone, and address fields map directly. Note that Twenty's Person object is actively developed; per GitHub issue #10422, the roadmap includes custom object conversion features. We map Contacts as People and preserve the original Friday CRM contact ID in a custom field for reconciliation. Any Contact without an email is flagged for manual review before import.

Friday CRM Deals map to Twenty CRM Opportunity. Deal name maps to Opportunity name, deal value maps to Opportunity amount, and deal stage maps to Opportunity stage. We preserve the original Deal ID and any associated Company link. Pipeline stage ordering from Friday CRM's kanban interface maps to the sequence of Twenty Opportunity stage values.

Friday CRM's customizable pipeline stage names and ordering map to Twenty CRM Opportunity stages by display sequence and label. We capture the stage probability percentages where defined in Friday CRM and set them on the corresponding Twenty stage. Stages with no probability mapping receive a default linear probability progression.

Friday CRM supports nine custom field types applied to Companies, Contacts, or Deals: text, number, single checkbox, multiple checkboxes, dropdown, date picker, URL link, multi-line text, and radio select. Twenty CRM's field type support is evolving and may not include all nine natively. We perform explicit type mapping: radio select converts to dropdown, multiple checkboxes split into separate boolean fields, single checkbox maps to a boolean, date picker maps to date, URL maps to link. We document every field type decision with the customer before migration.

Friday CRM stores notes linked to Contacts and Deals. We extract note text, timestamps, and author information from the export and map them to Twenty's activity or comment model. The association to the correct Person or Organization record is resolved via the Friday CRM record ID preserved during Contact and Company import. Notes without a parent record are held in a reconciliation queue.

Friday CRM tags appear as comma-separated values or array fields in the export for Contacts and Deals. We parse, deduplicate, and normalize tags before mapping them to Twenty's tagging or label system. The customer chooses the target tagging strategy during scoping based on how they use tags for segmentation in Friday CRM.

Friday CRM Owners map to Twenty CRM WorkspaceMembers by email match. We extract every Owner referenced on Contact, Company, and Deal records and resolve against the Twenty workspace. Any Owner without a matching WorkspaceMember in Twenty goes to a reconciliation queue for the customer's admin to provision before record import resumes.

Friday CRM does not expose file attachments via its documented CSV export or public API. We flag this limitation upfront and recommend users export attachments separately through the platform's UI before migration. We do not include attachment migration in the standard scope. The customer must manually re-attach files post-migration or use a file hosting integration.

Friday CRM integrates with Gmail, G Suite, Mailchimp, and RingCentral. Integration configurations, OAuth tokens, and connection credentials are not stored as migratable data. We do not migrate integration settings. Every connected integration must be reconfigured from scratch in Twenty CRM after migration, including re-authenticating OAuth connections and updating any automation rules that depend on those integrations.