Migrate from Vendasta to Twenty CRM

Vendasta Accounts represent SMB businesses managed by the agency partner. They map directly to Twenty Companies. The account schema includes standard fields (name, address, industry, contact info) and is stable across API versions. We use Company name as the dedupe key during import. Vendasta's account-level custom fields (partner-scoped) migrate to Twenty custom fields on the Company object, created in Settings → Data Model before import. Any enumerations in custom fields require explicit value mapping to avoid silent data loss.

Vendasta Contacts are tied to Accounts and carry partner-specific custom fields. They map directly to Twenty People records. We preserve name, email, phone, and lifecycle-stage data. If the Contact has a relationship to a Vendasta User (the agency employee), we resolve the owner by email against Twenty Members invited before import. Contact-level custom fields migrate as custom fields on the People object, with enumerated values explicitly mapped.

Vendasta Users (agency employees who manage SMB accounts) map to Twenty Members. We resolve by email match. Any Vendasta User without a matching Twenty Member is held in a reconciliation queue for the customer to provision before record import begins, because owner lookups on Company and People records require the Member to exist first.

Orders are created when a partner activates a product or service for an SMB account. Twenty CRM has no native order or commerce object, so we pre-create a custom Opportunity schema with fields for order number, line item count, total amount, order status, and order date. Active marketplace product line items from Orders are extracted per account and mapped to the corresponding Company in Twenty as custom fields or as Opportunity records with descriptive naming. The customer chooses between a single summary Opportunity per account or discrete Opportunity records per active order during scoping.

Subscriptions represent recurring billing relationships tied to active product activations. We map Subscriptions to the same custom Opportunity schema used for Orders, adding fields for billing frequency, subscription tier, start date, and renewal date. The subscription status (active, paused, cancelled) migrates as a custom picklist field on the Opportunity. If the agency maintains many active subscriptions per SMB account, we recommend creating a dedicated Subscriptions custom object in Twenty rather than overloading the Opportunity object.

Vendasta Invoices include line items, amounts, tax rates, discounts, and payment status. Since Twenty CRM has no native Invoice object, we extract invoice records as a structured data package (CSV or JSON) and attach them as Notes on the corresponding Company or Opportunity record in Twenty. The customer's admin can reference the original invoice data for billing reconciliation. If invoices represent a critical audit artifact, we create a custom Invoice object in Twenty with the relevant fields before import.

Partners define custom fields on Accounts and Orders via Vendasta's Custom Fields API. These fields are partner-scoped and may have inconsistent schemas. We extract the full custom field manifest during discovery, identify equivalent properties in Twenty's Data Model, and create any missing custom fields before importing records. Enumerated custom fields require explicit value mapping to avoid silent data loss. Fields that have no Twenty equivalent are flagged for the customer to decide whether to recreate as a new custom field or drop.

Vendasta's AI Employees are proprietary platform-native agents with no documented API schema and no equivalent in any conventional CRM system. Workflows that rely on AI Employees (automated lead qualification, content generation, client engagement) cannot be migrated directly. We identify every AI Employee in the account, document the business process it automates, and provide the customer with a manual rebuild guide for Twenty's workflow and automation capabilities. This is an excluded artifact.

Vendasta's automation module supports triggers based on email campaigns, product adoption, and upsell opportunities. Twenty v2.0 has a workflow engine but with a different trigger model, action types, and step logic. We do not migrate workflows as code. We deliver a written inventory of every active Vendasta Automation Workflow with its trigger conditions, steps, actions, and a recommended Twenty workflow equivalent. The customer's admin rebuilds them in Twenty post-migration. We flag any automations that depend on AI Employees as requiring full rebuild since the AI trigger has no destination equivalent.

Active marketplace products (listings, reputation tools, SEO services, advertising) are stored as line items on Vendasta Orders, not as standalone product records. The fulfillment status and activation state are embedded in the order record. We extract all active order line items per account, reconstruct the product activation history, and map them to custom multi-select fields on the Twenty Company record (e.g., active_products__c with values for Listings, Reputation, Social, SEO, Advertising). The customer's admin defines the complete product set during scoping.

Snapshot Reports provide SMBs with an automated assessment of their online presence across listings, reviews, and social channels. These are report artifacts rather than transactional records. We do not migrate Snapshot Reports to Twenty CRM because Twenty has no native reporting artifact equivalent. We extract a summary of each report as a Note attached to the corresponding Company record for reference. The customer's admin rebuilds reporting dashboards in Twenty's analytics views post-migration.