Migrate from Sharp CRM to Twenty CRM

Sharp CRM Company records map directly to Twenty's Company object. The company name becomes the display name, domain maps to the website field, and any industry or address fields map to the corresponding Twenty Company fields. Company is imported first because Contacts have a required lookup to Company — the relationship is resolved at import time by matching on company name or domain.

Sharp CRM Contact records map to Twenty's Person object. The first name, last name, email, phone, and address fields map to their Twenty equivalents. The contact-to-company link is resolved by looking up the associated Company by name or domain during the Person import. Any Sharp CRM contact without a matching Company in Twenty is flagged for manual resolution before the Person import phase begins.

Sharp CRM Deals map to Twenty Opportunities. The deal name becomes the Opportunity name, deal value maps to the amount field, and close date maps to the expected close date. Pipeline stage names vary by Sharp CRM account configuration and must be explicitly mapped to Twenty's Opportunity stage values during scoping. The deal's associated Company and primary Contact links are resolved at migration time by looking up the Company and Person records already imported.

Sharp CRM Tasks map to Twenty Tasks. Title, due date, assignee (resolved by email match to Twenty User), and completion status transfer directly. Open tasks are imported with their original due dates; completed tasks are imported with completed status and original completion timestamps preserved where available.

Sharp CRM call activities map to Twenty Tasks with the type set to call. Call disposition, duration, and notes transfer to custom fields on the Task where Twenty supports them, or to the task body as structured text. The timestamp of the call is preserved as the Task's due date for timeline ordering.

Sharp CRM email activities map to Twenty Tasks with the type set to email. The email subject and body transfer as task notes. The email timestamp preserves as the Task's due date. Attachments associated with email activities are exported to a file store and linked by record reference in Twenty.

Sharp CRM notes attached to Contacts or Companies map to Twenty Tasks with type set to note. The note body transfers as the task description. Notes are linked to the parent Person or Company by record reference resolved at migration time.

Sharp CRM pipeline stages are customer-configured and do not export with a standard schema. During scoping we ask the customer to provide their current stage names and order, then build an explicit stage-mapping table before the import. Each mapped stage is configured in Twenty before Opportunities are imported, so deal records land in the correct stage. Stages without a clear Twenty equivalent are flagged for the customer to configure before migration proceeds.

Sharp CRM is marketed toward diverse verticals, making custom fields likely in most customer accounts. We enumerate all custom fields during scoping, classify each by data type (text, number, date, picklist, checkbox, currency), and map them to the corresponding custom field in Twenty. Sharp CRM custom fields that have no clear Twenty equivalent are flagged for the customer to resolve before import. Custom fields are created in Twenty via the /metadata API before any data is imported.

Sharp CRM Owner records map to Twenty Users by email match. The owner name and email transfer. Active or inactive status is preserved in Twenty. Any Sharp CRM Owner without a matching email in Twenty is held in a reconciliation queue for the customer's admin to provision the corresponding user account before record import resumes.

Sharp CRM tags or labels on Contacts and Deals are exported as tag arrays. Tags are mapped to Twenty's tagging system by creating matching tags in Twenty and linking them to the migrated records. The tagging structure (flat labels vs. hierarchical) is documented during scoping, and any structural differences are flagged for the customer to decide on tagging taxonomy post-migration.