Migrate from Moskit to Twenty CRM

Moskit Contacts map to Twenty's Person object. We extract all standard fields (name, email, phone, custom properties) via the Moskit REST API and map them to the corresponding Twenty Person fields. The mapping includes any Brazilian Portuguese picklist values, which we preserve in a field-label glossary so administrators can rename labels post-migration. Person records are inserted before any Opportunity import so that the Account-Person relationship resolves at insert time.

Moskit Companies map directly to Twenty Companies. The Moskit domain and address fields map to Twenty's domain and address compound fields. The company record is the first object imported because both Person (linked to a Company) and Opportunity (linked to a Company) depend on the Company foreign key. We resolve Moskit's company ID to the new Twenty company UUID before inserting any related Person or Opportunity records.

Moskit Deals map to Twenty Opportunities. The dealstage property maps to Twenty pipeline stage values that we configure in the workspace before migration. Closed-Won and Closed-Lost reason custom fields map to Twenty custom fields with equivalent picklists. The pipeline assignment in Moskit maps to a Twenty pipeline that we create via the workspace schema editor before migration begins.

Moskit Activities (tasks, calls, meetings, notes) split into Twenty Tasks and Events based on activity type. Call activities map to Task with a task-subtype call field if Twenty has that field enabled; meeting activities map to Event with start and end timestamps preserved. Note-type activities map to Twenty Note records attached to the parent Person, Company, or Opportunity via ContentDocumentLink. Activity timestamps are preserved exactly as stored in Moskit to maintain the historical timeline.

Moskit Projects do not have a direct Twenty equivalent because Twenty ships without a native project module. We create a custom Project object in the Twenty workspace with fields for project name, description, start date, due date, status, and a custom Opportunity link field that holds the migrated deal reference. This requires pre-creating the custom object schema in Twenty before the Project data import, which we do via the workspace schema editor or direct API call.

Moskit pipeline stages migrate as Twenty pipeline stage values. Each Moskit pipeline becomes a Twenty pipeline, and stage names and order are replicated. Stage probability percentages from Moskit are stored as custom fields in Twenty since the base Opportunity object may not expose probability per stage by default. We configure this during the pre-migration workspace setup phase.

Moskit Users map to Twenty workspace Members. We extract every distinct user referenced on Contacts, Companies, Deals, and Activities and match by email against Twenty's user table. Any Moskit user without a matching Twenty account is placed in a reconciliation queue so the customer's admin can provision the account before record migration resumes. Inactive Moskit users are migrated with an inactive flag.

Moskit allows custom fields on Contacts, Companies, Deals, and Activities. These do not enumerate from a single API endpoint, so we query the schema per object type during extraction. We create equivalent custom fields in Twenty's workspace schema editor (or via API) before data migration, mapping Moskit field types (text, number, date, picklist) to the closest Twenty field type. Multi-checkbox picklists in Moskit may need to become multi-select picklists in Twenty, and we flag this type approximation during scoping.

Moskit's WhatsApp Business integration stores conversation metadata (timestamps, participant count, message count) linked to Contact records, but the actual message content lives in WhatsApp's infrastructure. We import the conversation metadata as a Note attached to the corresponding Person record in Twenty, with a note body that lists the WhatsApp thread reference, date, and message count. Full message history does not migrate from WhatsApp and must be exported separately from WhatsApp's own data export tools.

Moskit mass email campaign records and campaign membership data do not have a native Twenty equivalent (Twenty has no built-in mass email campaign module). We export campaign membership as a custom Campaign Membership object in Twenty with a Person lookup and campaign reference fields. Campaign content (templates, send history) is documented in a written inventory for the customer's admin to rebuild using their preferred email sending tool (e.g., Apollo, Instantly, Mailchimp) integrated with Twenty via Zapier or direct API.