Migrate from Vendasta to Freshsales

Vendasta Accounts represent the SMB businesses that channel partners manage. They map directly to Freshsales Accounts with the SMB's business name, address, and contact details. Account is the parent record in Freshsales, so we import it first to satisfy the AccountId lookup on Contact and Deal. Vendasta's per-client billing data (active marketplace products, subscription status) maps to custom fields on the Freshsales Account record.

Vendasta's contact model ties users to Accounts with partner-specific custom fields. We split into Freshsales Contact (qualified business contacts attached to the Account) and Lead (prospects not yet attached to a commercial relationship). Unqualified contacts with no active order history become Leads; contacts tied to active subscriptions or historical orders become Contacts. We preserve the original Vendasta contact lifecycle stage in a custom field for audit.

Vendasta Orders represent commercial transactions where a partner activates a marketplace product for an SMB Account. Active orders with pipeline intent (upsell, renewal, cross-sell) map to Freshsales Deals with the AccountId lookup resolved, the order total as Deal Amount, and the order status mapped to a Freshsales pipeline stage. Orders that represent completed billing transactions without sales intent are mapped as Notes or archived custom records rather than active Deals.

Vendasta Subscriptions represent recurring billing relationships tied to active product activations. Freshsales does not have a native subscription object at any tier. We extract subscription records during discovery, then create custom fields on the Account object (subscription_status__c, subscription_start_date__c, subscription_renewal_date__c, billing_frequency__c) to preserve the subscription context without creating a non-native object.

Vendasta partners define custom fields on Accounts and Orders via the Custom Fields API, scoped to the partner rather than the platform. We extract the full custom field manifest during discovery, validate each against Freshsales' available field types (text, number, date, picklist, multi-select), create matching Freshsales custom fields before import, and apply explicit value mapping for enumerated fields. Custom field schema differences between Vendasta accounts require per-customer validation.

Vendasta Notes and Snapshot Reports (automated online presence assessments for SMBs across listings, reviews, and social channels) migrate to Freshsales Note records linked via ContentDocumentLink to the parent Account. Snapshot reports are report artifacts rather than transactional records; we extract them as Note records with the report type and generation date preserved so that the customer's admin can reference them post-migration.

Vendasta Tasks associated with Accounts and Orders map to Freshsales Task records with the same subject, due date, status, and owner assignment. Task ownership resolves by matching Vendasta user email against Freshsales User email. Completed and open tasks migrate with historical timestamps preserved.

Vendasta AI Employees are proprietary platform-native agents with no documented API schema and no equivalent in Freshsales or any external CRM platform. We identify every active AI Employee in the account, document the business process it automates (lead qualification, content generation, client engagement), and provide a written rebuild guide for the customer to recreate equivalent automations in Freshsales Workflows and Freddy AI sequences. AI Employees cannot be exported or migrated as functional records.