Migrate from Verenia to Microsoft Dynamics 365 Sales

Verenia Quotes map to Microsoft Dynamics 365 Sales Quote or Opportunity depending on the customer's quoting workflow. We preserve quote number, line items (product, quantity, unit price, discount), status, expiration date, and customer association. If the customer uses Quote for final customer-facing documents, we map to the Quote object linked to the Opportunity. If quotes are internal pipeline records, we map to Opportunity directly and create Quote records only for signed or accepted quotes.

Verenia Orders carry configuration data, pricing, and customer association. We preserve order number, line items, totals, and status (pending, confirmed, shipped, closed). Orders with a closed-won status map to Opportunity with CloseDate and StageName set to Closed Won. Pending or in-progress orders map to Opportunity with the appropriate stage. Configuration data nested within orders is decomposed into structured metadata notes attached to the Opportunity for manual rebuild in Dynamics 365's CPQ tools.

Verenia Products (including SKUs, pricing rules, and bundle structures) map to Microsoft Dynamics 365 Sales Product2 records. We preserve product name, product code (SKU), description, base price, and pricing tier definitions. Bundle structures (parent products with mandatory or optional child products) are extracted as a structured metadata document rather than executable rules, because Microsoft Dynamics 365 Sales does not natively interpret guided-selling logic without a Power Apps or third-party CPQ extension.

Verenia stored guided-selling rules, compatibility constraints, and pricing tier logic within Product Configuration records. These do not map to any standard Microsoft Dynamics 365 Sales object. We extract them as structured metadata (JSON or CSV) and load them into a custom Configuration entity we create in the destination org, linked to the related Product2 and Opportunity via lookup. The customer's admin uses this documentation to rebuild configuration logic in Dynamics 365's Power Apps, third-party CPQ, or custom canvas apps.

Verenia Contact records (name, email, phone, company association) migrate directly to Microsoft Dynamics 365 Sales Contact. We use email as the dedupe key and preserve all standard contact fields. Custom contact properties (sales rep, territory, product interest) are mapped to custom Contact fields that we create in the destination schema before import.

Verenia Company records map to Microsoft Dynamics 365 Sales Account. We preserve company name, address, industry, domain, and any custom fields. The Account record is created before Contact import so that the parent Account lookup is satisfied at the moment of Contact insert. Company-to-contact relationships are preserved through the Account-Contact relationship model in Dynamics 365.

Verenia User records map to Microsoft Dynamics 365 Sales User records by email match. We extract all Owner references from Quote, Order, Contact, and Company records and resolve them against the destination User table. Any Verenia Owner without a matching Dynamics 365 User goes to a reconciliation queue for the customer's admin to provision before record import continues. Inactive Verenia users are mapped to inactive Users in Dynamics 365 to preserve historical assignment.

Quote PDFs, order confirmations, and configuration screenshots extracted from Verenia export archives are loaded into Microsoft Dynamics 365 Sales . We link them to the relevant Quote, Order, or Opportunity record via the standard Attachment or Note mechanism. If the customer's Dynamics 365 environment is configured with Microsoft 365 integration (SharePoint or OneDrive for document management), we map files to the aligned document library location for native Teams and Outlook access.