Migrate from Verenia to Twenty CRM

Verenia Contact records (name, email, phone, company association) map directly to Twenty People. Standard field mapping applies: firstName, lastName, email, phone. Company association maps to the Twenty Company lookup once the Company object is populated. Custom contact properties migrate via our field-mapping workflow into Twenty custom fields created in Settings → Data Model before import.

Verenia Account records map to Twenty Company. Fields including name, address, industry, and domain map to Twenty Company displayName, address fields, and custom fields. We preserve company-to-contact relationships during migration to maintain referential integrity: Company records are imported first so that People records can resolve the companyId lookup at insert time.

Verenia Quotes map to Twenty Opportunity. The Quote header fields (quote number, status, created date, total amount) map to Opportunity name, stageName, createdAt, and amount. Quote status (Draft, Sent, Accepted, Lost) maps to Twenty Opportunity stage values that we configure in Settings → Data Model before import. Original Verenia quote numbers are preserved in a custom field for audit.

Verenia Quote line items (product, quantity, unit price, discount, line total) do not map to a native Twenty object. We either create a Custom Object (QuoteLineItem) with fields for product, quantity, unitPrice, discount, and totalPrice, or we embed line item summaries as structured text in the Opportunity description field. The customer selects the preferred approach during scoping. Product references are resolved against the Products import.

Verenia Orders map to Twenty Opportunity with stageName set to Closed Won. Order metadata (order number, date, customer, total) maps to Opportunity name, createdAt, amount, and the related Company and People records. Pending orders (not yet fulfilled) map to Opportunities with a pending stage value that the customer configures in Twenty.

Order line items follow the same treatment as Quote line items: either a Custom Object or embedded summary in the Opportunity record. Configurations nested within orders require decomposition; we extract the bundle structure as structured metadata and document which items represent parent bundles versus child components.

Verenia Product catalog items (name, SKU, pricing, bundle flag) do not map to a native Twenty object. We create a Product custom object in Twenty with fields matching the Verenia product schema: name, sku, basePrice, costPrice, and isBundle. Pricing rules (volume tiers, discounts) are extracted as structured metadata and documented for manual rebuild in the customer's CPQ workflow.

Verenia stored guided-selling rules and product configuration logic. These do not map 1:1 to Twenty. We extract configuration metadata as structured records in a Configuration custom object: parent product, constraint rules, compatibility matrix, and pricing logic. We document which rules require manual rebuild in Twenty's workspace. Configuration artifacts that cannot be structured migrate as Notes attached to the relevant Product record.

Verenia User records map to Twenty Members. We resolve owners by email match against the Twenty Members list. Any Verenia User without a matching Twenty Member is held in a reconciliation queue for the customer's admin to provision before record import resumes. Owner assignment on migrated records is remapped to the resolved Member records.

Quote PDFs, order confirmations, and configuration screenshots are extracted from exported archives. File naming conventions vary across exports, so we normalize paths before loading. Attachments are linked to the relevant Twenty record (Opportunity, People, or Company) via Twenty's file attachment system. We flag any attachments that cannot be matched to a parent record for manual review.

Verenia notes attached to Quotes, Orders, or Contacts migrate to Twenty Notes linked to the corresponding Opportunity, People, or Company record. Note body migrates as plain text. If rich formatting was used in Verenia, we preserve a plain-text version and note the limitation.