Migrate from m-savvy to Twenty CRM

M-savvy Contacts map to Twenty People records. The m-savvy contact's name, email, phone, address, lifecycle stage, and owner assignment transfer to Twenty People fields. We create standard fields in Twenty Settings Data Model before import, then bulk-insert People records using the resolved owner email as a Twenty workspace member reference. Any m-savvy contact properties without a direct Twenty equivalent become custom fields on the People object.

M-savvy Account records map directly to Twenty Company. The account name, industry, size, billing address, and domain transfer to Company fields. We insert Companies before People so that the Company-People relationship resolves at import time. The Company domain or website field is used as the dedupe key to prevent duplicate company creation when multiple contacts share the same organization.

M-savvy Deals map to Twenty Opportunity records. Stage, amount, close date, probability, and custom deal properties transfer to the Opportunity object. We pre-configure stage values in Twenty Settings before migration so that imported opportunities land in the correct stage. Any custom stage names from m-savvy become Twenty stage field options.

M-savvy Leads are distinct from Contacts in m-savvy's data model. We import Leads as Twenty People records with a type or status field set to Lead to preserve the lead-contact distinction that Twenty does not enforce natively. Lead source and lead score from m-savvy become custom fields on the People record.

M-savvy activity records (calls, emails, meetings, tasks, notes) map to Twenty Task or Note records linked to the parent People or Company record. Activity timestamps preserve to maintain chronological history. We resolve the parent record by matching the m-savvy contact or account ID to the newly created Twenty People or Company record ID.

M-savvy custom objects require live API inspection during discovery because no public schema documentation exists. We enumerate each custom object type and its field definitions from the m-savvy API, then replicate the schema in Twenty Settings Data Model before importing. Custom object records insert after standard objects to satisfy any lookup relationships to People, Company, or Opportunity.

M-savvy stores attachment files separately from record data and requires a separate file-export pass. We download files from m-savvy's file storage endpoints, stage them locally, then upload to Twenty and relink each file to its parent record ID. If a parent record failed to migrate, the attachment is flagged and held for manual review rather than orphaned in Twenty.

M-savvy pipeline definitions and custom stage names read from the m-savvy schema during discovery. We configure the matching stage values in Twenty Settings before opportunity import. If m-savvy has stages with no equivalent in Twenty's default set, we create them as custom stage options. Stage order and probability percentages transfer to Twenty stage configuration.

M-savvy owners resolve by email match to Twenty workspace members. We extract every distinct owner referenced on Contact, Account, Deal, and Activity records and match against the Twenty Members list. Any m-savvy owner without a matching Twenty member enters a reconciliation queue for admin provisioning before record import proceeds.

M-savvy lead source values (campaign, referral, organic, etc.) do not exist as standard fields in Twenty People. We create a custom select field on People during schema setup and populate it from m-savvy's lead source property during import.