Migrate from Verenia to Pipedrive

Verenia Quotes map to Pipedrive Deals. Each Quote's header fields (quote number, created date, status, owner) map to Deal title, add_time, stage, and owner_id. Quote line items map to Deal Products via Pipedrive's deal_product relationship. Since Verenia is shut down and quote numbering sequences are not preserved by default, we generate a cross-reference table mapping original Verenia quote IDs to new Pipedrive Deal IDs for audit purposes. Note that Pipedrive's native Quote object is only available on the Power and Enterprise tiers; on lower tiers, Deals serve as the quote container.

Verenia Orders map to Pipedrive Deals where the order status (closed-won, pending, fulfilled) maps to the appropriate Pipedrive stage. We decompose nested product configurations within orders into separate Deal Product entries. Closed-won orders from Verenia become closed-won Deals in Pipedrive, preserving the won date and order value. Pending orders become Deals in a pre-close stage. The original order number is stored in a custom Deal field for reconciliation.

Verenia's guided-selling rules, bundle structures, compatibility constraints, and pricing tier logic are extracted as structured metadata records rather than migrated as executable rules. Pipedrive's Product object stores products with variants, but does not natively interpret CPQ configuration logic. We deliver a configuration inventory document listing every Verenia product rule, its trigger conditions, and recommended Pipedrive equivalents (such as product variants, pricing formulas, or workflow automations) for the customer's admin to rebuild.

Verenia product catalog items map to Pipedrive Products. Product name, SKU, description, and base pricing transfer directly. Pricing rules such as volume discounts, tiered pricing, and bundle pricing do not transfer as executable rules — we map them as structured pricing metadata and document the recommended rebuild in Pipedrive's pricing setup.

Verenia Contact records with name, email, phone, company association, and custom properties migrate directly to Pipedrive Person. Standard field mapping applies. We deduplicate by email during the import phase. Custom contact properties are handled via our field-mapping workflow, with custom field types matched to Pipedrive's field type equivalents (text, number, date, single-select, multi-select).

Verenia Company records map to Pipedrive Organization. Company name, address, industry, website, and standard fields migrate directly. We preserve the company-to-contact relationship by importing Organizations first and resolving the organization_id on each Person record during the Contact import phase. This maintains referential integrity in Pipedrive's CRM data model.

Verenia User records referenced as Quote owners, Order owners, and record assignees are mapped by email match against Pipedrive User accounts. The customer's Pipedrive admin provisions active Users before migration. Any Verenia User without a matching Pipedrive User is placed in a reconciliation queue. Owner assignment on Deals and Persons is remapped post-migration to the provisioned Users.

Quote PDFs, order confirmations, and configuration screenshots stored in Verenia export archives are extracted and linked to the corresponding Pipedrive Deal or Person record. File naming conventions from Verenia exports vary; we normalize file paths and store the original Verenia document name in a custom field for traceability. Attachments exceeding Pipedrive's storage limits require additional handling and are flagged during scoping.

Verenia Quote line items map to Pipedrive Deal Products linked to the parent Deal. Each line item's product reference, quantity, unit price, discount, and total price transfer directly. Where Verenia line items included bundle components (sub-items within a configured product), we decompose them into individual Deal Product rows and flag the decomposition in the migration log.

Verenia pricing rules including discount schedules, volume thresholds, and customer-specific pricing tiers are extracted as structured metadata and mapped to custom fields on Pipedrive Deals and Products. These do not become active pricing logic in Pipedrive; they are documented for the customer's admin to implement via Pipedrive's pricing tools or workflow automations post-migration.