Migrate from Kuverto to Twenty CRM

If Kuverto stores contact records as part of its integration data or workflow context, these map to Twenty CRM Person objects. The source contact name, email, phone, and any custom properties migrate to Twenty's typed fields (displayName, email, phoneNumber) or custom fields pre-created in the destination schema. We resolve duplicate persons by email domain during import and flag remaining duplicates for customer review.

Kuverto integration data may include company records synced from connected platforms. These map to Twenty CRM Company objects with name, domain, address, and industry fields. Company is imported before Person so that the Person.CompanyId lookup relationship is satisfied at insert time. Any company-to-company hierarchy in Kuverto data maps to Twenty's companyRelation object.

Deals tracked in Kuverto (e.g., via CRM integrations inside workflows) map to Twenty CRM Opportunity. The Kuverto deal name, stage, amount, close date, and probability migrate to Twenty's Opportunity name, stageName, amount, closeDate, and probability. We pre-create Twenty pipeline stages matching the Kuverto pipeline configuration during schema setup.

Kuverto workflow execution logs that represent business activities (meetings scheduled, calls logged, tasks created) map to Twenty CRM Task and Event objects. The original Kuverto timestamp is preserved as ActivityDate. We resolve the parent Person or Company reference by matching email or domain to the migrated Person or Company record.

Kuverto stores OAuth tokens and API keys for connected platforms (Salesforce, HubSpot, Slack, Gmail, Stripe). These credentials are not portable between platforms. We produce a complete inventory of every Kuverto integration connection, the scopes it uses, and the re-authentication steps required in Twenty CRM or an equivalent middleware. The customer re-authenticates each integration post-migration before go-live.

Kuverto agents contain LLM prompts, instructions, memory settings, and tool permissions that have no equivalent storage construct in Twenty CRM. We do not migrate agents as executable records. Instead, we extract and document every agent configuration — name, model, system prompt, tool definitions, and memory settings — as a written specification. The customer uses this document to rebuild agents in Twenty or a dedicated AI agent platform post-migration.

Kuverto Workflow Mode sequences (trigger conditions, sequential steps, branching logic) cannot be transferred to Twenty CRM's beta workflow feature because the execution models differ. We document every Kuverto workflow as a written specification including trigger, steps, conditions, and actions. The customer rebuilds workflows in Twenty's Workflow feature or an external automation platform. Workflows are not migrated as code.

Kuverto Custom Tools define API endpoint specifications, parameter schemas, and response parsing logic used by agents. Twenty CRM does not have an equivalent custom tool definition model. We extract the complete tool definitions (endpoint URL, method, parameters, headers, response schema) as a written technical document that the customer's developers use to implement equivalent functionality as Twenty CRM API integrations or webhook-based custom objects.

Kuverto team workspace roles (editor, viewer, integration manager) map to Twenty CRM workspace roles. We document the permission scope per Kuverto role and map it to the equivalent Twenty workspace role. Custom permissions that have no direct Twenty equivalent are flagged for the customer's admin to configure post-migration.

Kuverto's AO consumption is a billing metric tracked internally by Kuverto's metering system. It is not user-owned data and has no equivalent in Twenty CRM. Historical AO usage is not migrated; we advise customers to audit their AO consumption in Kuverto before the migration window if they want to evaluate baseline costs on a replacement automation platform.