Migrate from myCRMS.com to Twenty CRM

myCRMS.com Company records map directly to Twenty's Company object. The company domain name is used as the unique dedupe key during CSV import per Twenty's import documentation. We export Companies first because Twenty requires the 'one' side of one-to-many relationships to exist before People can reference them via companyId. Standard fields (name, domain, address, industry) map to Twenty Company fields of equivalent name.

myCRMS.com Contact records map to Twenty's People object. Each Contact's linked Company resolves to a companyId lookup during transform. Email address serves as the dedupe key per Twenty's import uniqueness rules. Custom fields on Contact migrate to Twenty custom fields that we pre-create in Settings → Data Model before the CSV import phase. Activity timestamps and owner assignments migrate from fields exposed in the myCRMS.com export.

myCRMS.com Deal records map to Twenty's Opportunity object. Deal stage maps to Twenty Opportunity Stage; pipeline data maps to a Twenty Sales Process or Record Type we configure before migration. The linked Company and People records are resolved via companyId and peopleId lookups at migration time. Closed-won and closed-lost dates migrate as Opportunity close date fields.

myCRMS.com pipeline stages map to Twenty Opportunity Stage values, which we configure in Settings → Sales Process before importing Opportunities. Each stage gets a probability percentage migrated from the source. The pipeline name becomes a Twenty Record Type label for visual and workflow scoping.

myCRMS.com Smart Lists are filtered saved views of contact sets managed in the UI. These do not migrate as data or code. We deliver a written inventory of every active Smart List with its filter conditions and contact count so your admin can recreate them as Saved Views in Twenty's filter builder. This is documented separately from the data migration scope.

Any custom fields discovered on myCRMS.com Contact records are audited during the pre-migration review. We pre-create matching custom fields in Twenty's Settings → Data Model on the People object before CSV import runs, per Twenty's requirement that fields must exist before import. Field type mapping (text to text, date to date, picklist to select) is documented in the mapping spec.

Custom fields on myCRMS.com Deal records map to custom fields on Twenty Opportunity, pre-created in Settings → Data Model before import. Cross-object lookups (e.g., a Deal referencing a custom object) are resolved at migration time using the target object's unique identifier as the relation key.

If myCRMS.com contains custom objects (schema-dependent and tier-dependent per limited platform docs), we map them to Twenty Custom Objects. We pre-create the destination schema in Twenty including all fields, field types, and lookup relationships, before importing any custom object data. Custom object records import last per Twenty's import dependency order.

myCRMS.com Owner assignments on Contact, Company, and Deal records map to Twenty User records. We resolve owners by email match. Per Twenty's documentation, users must accept their workspace invitations before data import begins; otherwise owner lookups resolve empty and require post-import correction. Owners without a matching Twenty User are placed in a reconciliation queue for your admin to provision before record import resumes.

myCRMS.com activity records (notes, tasks, meeting records) export as activity timestamped entries. These migrate to Twenty Note objects linked via ContentDocumentLink to the parent People, Company, or Opportunity record. Activity ordering is preserved by setting the Twenty record's creation timestamp to the original myCRMS.com activity timestamp. The migration service does not migrate file attachments embedded in notes via CSV; these require manual re-upload or a separate API-based migration engagement.