Migrate from Smart CRM Online to Twenty CRM

Smart CRM Online Contact records map to Twenty Person. We extract name, email, phone, and company association from the CSV. Since the CSV flattens Company references to an ID or name string, we import Companies first and resolve the Company ID to the Twenty Company record ID before inserting each Person. Any Contact without a matching Company receives a placeholder Company record to avoid orphaned Person entries. Tags attached to a Contact in Smart CRM Online migrate as comma-separated text to the Person's standard tags field or a custom multi-select field pre-created during schema setup.

Smart CRM Online Company records map to Twenty Company. We import Companies before Persons to satisfy the foreign-key dependency. Domain, industry, employee count, address, and account owner fields map to their Twenty equivalents. Companies with no associated Contacts are retained as standalone Company records. If Smart CRM Online exports a Company record without a primary contact, we flag it for the customer to confirm whether to create a placeholder Person or leave the Company unattached.

Smart CRM Online Deals map to Twenty Opportunity. The deal name, value, close date, stage, and owner map to Opportunity.name, amount, closeDate, stage, and accountOwner respectively. The stage value is mapped using the stage rename table defined during discovery. Deals without a linked Company in the CSV are assigned to the most recently created Company record matching the Contact name, or held in a reconciliation queue if no match is found.

Smart CRM Online pipeline stages are configurable and export with the Deal record. We extract the full ordered list of stages during discovery, map each to a Twenty Opportunity stage with matching order, and configure the stage probability if Smart CRM Online stores it. Custom stage names are preserved verbatim unless they exceed Twenty's field length, in which case we truncate and flag the change.

Smart CRM Online call logs associate with Contact or Deal records. We migrate them as Twenty Task records with the call subtype set, preserving the call disposition, duration, and timestamp. The Task is linked to the migrated Person or Opportunity record using the reconstructed association. If the original Contact or Deal cannot be resolved, the Task is linked to the closest matching Company record.

Smart CRM Online email engagement records migrate as Twenty Task records with the email body preserved in the task body field. Subject, timestamp, and direction (sent or received) are stored as separate task fields. The task is linked to the Person record when the email is Contact-scoped. Email attachments are not included in the standard migration scope; they require a separate file-handling engagement.

Smart CRM Online meeting records map to Twenty Event with start time, end time, location, and description preserved. The meeting is linked to the Person record for Contact-scoped meetings or to the Opportunity for Deal-scoped meetings. Attendee names are stored in the event description field rather than as EventRelation records, since the CSV does not include structured attendee references.

Smart CRM Online Notes attached to Contact or Deal records migrate as Twenty Note records. We preserve the note body, author (mapped to the owner by email match), and creation timestamp. Notes are linked to the parent Person or Opportunity using the identifier resolution built during the Contact and Deal import phases. Notes without a resolvable parent are attached to the closest matching Company record.

Smart CRM Online permits custom fields per object, but no public schema documentation exists. During discovery we request a full data export, compare field names against the standard object schema, and identify which fields are custom. We pre-create every custom field in Twenty's Settings → Data Model before the import run. Unmapped custom fields are presented to the customer for explicit mapping decisions. Fields with picklist values in Smart CRM Online are created as select fields in Twenty with the same options.

Smart CRM Online Owners referenced on Contact, Company, and Deal records are resolved by email match against the Twenty workspace User table. The customer must invite all team members to Twenty and confirm their acceptance before we run the migration, because Twenty requires users to exist before record imports can reference them as accountOwner. Owners without a matching Twenty User are held in a reconciliation queue for manual provisioning.

Tags on Contact or Company records in Smart CRM Online are extracted as a list and stored in a pre-created multi-select picklist field on the Person or Company object in Twenty. The customer chooses during scoping whether to preserve all tags or consolidate to a core set. Tags used for classification rather than CRM association are migrated as Topic records with TopicAssignment linking.