Migrate from Verenia to Freshsales

Verenia Contact records map directly to Freshsales Contact. Standard fields (first_name, last_name, email, phone, company) map to Freshsales Contact equivalents. Custom contact properties are handled via field-level mapping against Freshsales custom fields. The Freshsales Contact object serves as the primary person record; we create Contacts before Deals to satisfy lookup dependencies.

Verenia Company records map to Freshsales Account. Company name, address, industry, and website fields map directly. The company-to-contact relationship is preserved via Freshsales Account-Contact lookup so that viewing an Account shows associated Contacts. If the Verenia export contains a company domain, it populates the Freshsales Website field.

Verenia Quotes map to Freshsales Deals on Growth plan ($9/user) because the Quotes object is only available on Pro ($39/user) and Enterprise. If the customer is on Pro or Enterprise, we use Freshsales Quotes directly. On Growth, Quote fields (line items, totals, status, customer association) map to Deal custom fields or Notes, and we deliver a written mapping table for the customer to configure the Deal form as a quote proxy. Original Verenia Quote numbers are preserved in a custom field verenia_quote_number__c for audit cross-reference.

Verenia Orders map to Freshsales Deals with Closed Won stage where applicable. Order totals, dates, and line items map to Deal fields or related Product records. Pending Orders map to Deals in the appropriate pipeline stage. The original Verenia Order number is preserved in a custom field verenia_order_number__c. Configuration data nested within Orders is extracted as structured metadata and attached to the Deal as Notes or a custom field, since Freshsales does not natively support CPQ configuration records.

Verenia guided-selling rules and product configuration logic do not transfer as executable rules to Freshsales, which has no native CPQ configuration engine. We extract configuration metadata as structured records (bundle components, compatibility constraints, pricing tiers) and load them as Notes attached to the relevant Product records or as custom fields on Products. The customer receives a written configuration inventory documenting which rules require manual rebuild in Freshsales Product or a third-party CPQ app if the Pro/Enterprise plan's CPQ add-on is activated.

Verenia Product catalog items map to Freshsales Product2 records. Product name, SKU (hs_sku equivalent), unit price, and description map directly. Pricing rules, discount tiers, and bundle pricing from Verenia are not preserved as executable rules in Freshsales; we document them as structured metadata on the Product2 record so they can be re-implemented manually. Price Book entries are created in Freshsales to support the Product-to-Deal pricing model.

Verenia User records map to Freshsales User for Owner assignment purposes. We match by email address. Any Verenia User without a matching Freshsales User is held in a reconciliation queue for the customer's admin to provision before Deal and Contact import. Inactive Verenia users are mapped to inactive Freshsales Users to preserve historical assignment.

Quote PDFs, order confirmations, and configuration screenshots extracted from Verenia archived exports are loaded into Freshsales as File attachments linked to the parent record (Contact, Account, or Deal). File naming conventions vary across Verenia export artifacts; we normalize file paths and attach each document to the correct parent record using the document metadata from the export.