Migrate from Verenia to Salesforce Sales Cloud

Verenia Quotes map to Salesforce Quote records linked to Opportunities if Salesforce CPQ is in use. If Salesforce Sales Cloud without CPQ is the destination, Quotes map to Opportunity with Quote fields (subtotal, discount, total) stored as Opportunity fields or custom fields. The Verenia quote status (Draft, Sent, Accepted, Expired, Revised) maps to Salesforce QuoteStatus or to Opportunity StageName depending on destination configuration. Original Quote document numbers are preserved in a custom field verenia_quote_number__c for audit cross-reference.

Verenia Orders map to Salesforce Opportunities with StageName = 'Closed Won' for straightforward migrations, or to the Salesforce Order object if the destination org includes Order Management. Order date, total amount, and customer association migrate as Opportunity fields. Line items from Verenia Orders map to OpportunityLineItem with Pricebook2 and Product2 resolved from the Product catalog mapping.

Verenia Products map to Salesforce Product2 records. The Verenia product code (SKU) maps to ProductCode. Standard Price Book entries are created during import. Verenia pricing tiers (volume discounts, tiered pricing) are extracted as structured metadata and documented for rebuild in Salesforce CPQ Price Lists and Pricing Procedures.

Verenia guided-selling rules, bundle structures, compatibility constraints, and option dependencies do not map as executable logic to Salesforce CPQ. We extract these rules from the export artifacts as structured metadata and write them to custom fields on Product2 (verenia_config_rules__c, verenia_bundle_structure__c, verenia_constraints__c). This documentation becomes the configuration brief for rebuilding rules in Salesforce CPQ Advanced Product Configuration.

Verenia Contact records with name, email, phone, and company association migrate directly to Salesforce Contact. Standard field mapping applies. Custom contact properties are handled via our field-mapping workflow. The Verenia contact ID is preserved in a custom field verenia_contact_id__c for audit and reconciliation.

Verenia Company records map to Salesforce Account. The company name, address, and industry fields migrate as standard Account fields. Account is created before any Contact import so that the AccountId Lookup relationship is satisfied at the moment of Contact insert. We use the Verenia company ID as a dedupe key during import.

Verenia User records map to Salesforce User records by email match. Owner assignment on Quotes, Orders, and Contacts is remapped to active Salesforce Users post-migration. If a Verenia User has no matching Salesforce User, the record is assigned to the migration admin and flagged in the reconciliation report for the customer's admin to provision or reassign.

Verenia Quote PDFs and order confirmation documents are extracted from archived export folders, normalized by filename convention (Quote ID, date, customer name), and loaded into Salesforce as ContentDocument records with ContentDocumentLink pointing to the parent Quote or Opportunity. File naming normalization handles inconsistent naming conventions from the legacy export artifacts.

Product configuration screenshots and visual rule exports from Verenia migrate as ContentDocument linked to the corresponding Product2 record. These serve as visual references for the admin rebuilding the configuration rules in Salesforce CPQ.

Verenia volume-based and tiered pricing structures are extracted as structured data and mapped to Salesforce PricebookEntry records with custom fields capturing tier breakpoints and discount percentages. The Pricebook2 is set as the Standard Price Book. Volume pricing logic is documented separately for rebuild in Salesforce CPQ Price Lists.

Verenia Quote line items map to Salesforce QuoteLineItem (if Salesforce CPQ is in scope) or OpportunityLineItem (if Sales Cloud without CPQ). We resolve the Pricebook2 reference, the Product2 reference, and the parent Quote or Opportunity at migration time. Quantity, UnitPrice, and Discount migrate directly. Bundle line items from Verenia are decomposed to individual line items with a custom field verenia_bundle_parent__c linking them to the parent bundle for rebuild reference.

Verenia approval workflows (quote discount thresholds, multi-tier sign-offs) are extracted as process documentation with the rule conditions, approver assignments, and escalation paths. We deliver this as a structured inventory document. Salesforce Quote Processes and Approval Processes rebuild is not included in the migration scope; the document guides the customer's admin or implementation partner.