Migrate from Vendasta to Nutshell

Vendasta Account records represent the SMB businesses managed by the partner agency and map directly to Nutshell Company records. The Account name, address, phone, website, and lifecycle stage fields map to the corresponding Nutshell Company fields. Account is the parent record in Vendasta's data model and must be created in Nutshell before any related Contact or Order data is imported to satisfy the Company-Person relationship.

Vendasta Users and Contacts tied to an Account map to Nutshell Person records linked to the corresponding Company. Vendasta's contact lifecycle stage, custom contact fields, and partner-scoped custom properties migrate as Nutshell Person custom fields. We validate that all enumerated custom field values from Vendasta are explicitly mapped to Nutshell picklist values or free-text equivalents to avoid silent data loss during import.

Vendasta Orders contain line items representing activated marketplace products (listings, reputation, SEO, advertising services) along with pricing, status, and custom fields. Nutshell has no native Order object, so we reconstruct order history as custom fields on the Company record. Active product activations are stored as multi-select picklists or tags on the Company; total order value and order count are stored as numeric custom fields. Each Order's status and creation date are preserved for historical reporting.

Vendasta Subscriptions represent recurring billing relationships tied to active product activations and map to Company-level custom fields in Nutshell capturing subscription status, billing frequency, and recurring revenue amount. We extract the Subscription object fields (billing cycle, start date, product list) and map them to typed Nutshell custom fields. Subscriptions without an active Account parent are flagged during scoping for manual resolution.

Vendasta Invoices include line items, tax rates, discounts, and payment status but have no native equivalent in Nutshell. We extract invoice metadata (invoice number, date, amount, status, due date) and store it as a structured set of Company custom fields. If invoice history is extensive, we recommend creating a separate invoice log spreadsheet as a reference artifact rather than importing each invoice as an individual record, since Nutshell's data model is not optimized for accounting records.

Vendasta partner-scoped custom fields on Accounts and Orders require pre-creation in Nutshell before migration. We extract the full custom field manifest during discovery, validate field types against Nutshell's supported types (text, number, date, currency, multi-select picklist, checkbox), and create any missing fields before importing records. Enumerated fields with specific allowed values require explicit value mapping between Vendasta and Nutshell picklist options.

Vendasta Owner records map to Nutshell Users by email address. We extract every distinct Owner referenced on Account, Contact, Order, and Subscription records and match against the Nutshell destination account's user list. Owners without a matching Nutshell User go to a reconciliation queue for the customer to provision before record import resumes, because OwnerId references are required on most standard Nutshell records.

Vendasta automation Workflows are not migrated to Nutshell as code. The two platforms use fundamentally different automation models: Vendasta Workflows trigger on email campaign engagement, product adoption, and upsell opportunities tied to its marketplace model; Nutshell's workflow builder operates on Opportunity stage changes, task assignments, and contact activity. We deliver a written inventory of every active Vendasta Workflow with its trigger, conditions, actions, and recommended Nutshell workflow equivalent. The customer's admin rebuilds them post-migration.