Migrate from Sentian Solutions to Twenty CRM

Sentian Solutions contact records map directly to Twenty People objects. The first name, last name, email, phone, and job title fields transfer as their Twenty equivalents. Each People record requires a linked workspace member (owner) resolved by email match against Twenty Members — records without a matching owner land with an unassigned status until manually linked.

Sentian Solutions company or organization records map to Twenty Companies objects. The company name, domain (website URL), and any industry or employee-count properties migrate to their corresponding Twenty fields. Parent-child company hierarchies in Sentian Solutions map to the Companies object via the Parent ID field in Twenty. Multi-company contact associations in Sentian Solutions collapse to one primary companyId on the Twenty People record, with secondary associations preserved as Notes for reference.

Sentian Solutions deal records map to Twenty Opportunities objects. Deal name, amount, expected close date, stage, and owner fields transfer directly. Sentian Solutions deal stages map to Twenty Opportunity stage values via value-by-value mapping — if the stage names differ, we create a mapping table before migration. Opportunities link to Companies via the companyId relation, which must be resolved after the Companies migration completes.

Sentian Solutions engagement records (calls, emails, meetings, tasks) transform into Twenty Tasks. Each Task captures the activity type, subject line, body content, original timestamp, and assignee. The assignee resolves via email match to Twenty workspace members. Call and email engagement types map to Tasks with Type='Call' or Type='Email' respectively. Meeting records with start/end times may map to Twenty Events if the organization's Twenty instance has the Events object enabled.

Free-form notes attached to Sentian Solutions contacts, companies, or deals migrate as Twenty Notes records. Each Note preserves its original creation timestamp, body content, and author (linked to a Twenty workspace member by email). Notes attach to the parent object (People, Companies, or Opportunities) in Twenty via the generic note associations model.

File attachments stored on Sentian Solutions records re-upload as Note attachments in Twenty. File size limits and supported formats depend on Twenty's attachment handling — we preserve the original file URL as a custom link field if the file cannot be directly attached due to size constraints.

Sentian Solutions owner or user references resolve by email against Twenty Workspace Members. We flag any owner email that does not match an existing Twenty member before migration — your team must invite those users to Twenty first, or assign their records to a fallback member. Owner resolution failures prevent record import for records depending on that owner.

Sentian Solutions custom properties on contact records require pre-creation in Twenty's Settings → Data Model before migration runs. We deliver a field creation plan listing each custom property's name, data type, and pick-list values so your Twenty admin can create the fields in advance. During migration, custom property values write to the corresponding custom field on the People record.

Company-level custom properties in Sentian Solutions map to custom fields on Twenty Companies objects. Same pre-creation requirement applies — fields must exist in Twenty before the migration run. Industry, employee count, and annual revenue are common custom fields that may need to be created as Number or Text fields rather than relying on non-existent standard fields in Twenty.

Sentian Solutions custom objects map 1:1 to Twenty custom objects. The custom object schema (field names, types, relations) must be recreated in Twenty via the Settings → Data Model → Create Custom Object workflow before migration. Custom object associations that represent many-to-many relationships require a junction object in Twenty — we flag these during the mapping phase and deliver a schema recommendation.

Twenty sets CreatedAt at migration time and does not allow backdating records to preserve original create timestamps from Sentian Solutions. We create a custom field (e.g., Original_Create_Date__c) on People, Companies, and Opportunities to preserve the source create date for reporting continuity.

We store Sentian Solutions' internal record ID on each migrated record as a custom text field for traceability, delta-run de-duplication, and rollback reference. This field is critical for identifying which Twenty record corresponds to which Sentian Solutions record if reconciliation is required post-migration.