Migrate from Wice CRM to Pipedrive

Wice Organization records map directly to Pipedrive Organization. The Wice Orga name becomes the Organization name, and Wice's address, phone, and custom properties map to their Pipedrive equivalents. We export Organizations first so that the Pipedrive Organization ID is available for Contact linkage resolution during the Contact import phase.

Wice Contact records map to Pipedrive Person. We resolve the Organization link (Wice's OrgaId) against the imported Organization to populate the Person's Org ID in Pipedrive. Email, phone, address, and custom fields migrate 1:1. Any Wice Contact without a valid Organization link is imported as a standalone Person with a reconciliation flag for the customer to review.

Wice Deal records map to Pipedrive Deal. Each Deal carries the Wice pipeline stage name (e.g., 'Proposal Sent', 'Negotiation'), which we explicitly map to a Pipedrive Stage within the customer's target Pipeline. Stage mapping is captured during discovery using the customer's actual Wice stage names and Pipedrive stage names as a two-column table before any Deals are written.

Wice allows fully custom pipeline stages per installation, and these are stored as free-form values on Deal records. We capture every distinct Wice stage name present in the data during discovery and generate a Pipedrive stage-mapping table. The customer selects or creates matching Pipedrive stages in their pipeline before migration. Stage probability percentages are set on Pipedrive stages post-creation.

Wice Projects contain tasks, assignees, and status fields. Pipedrive does not have a native Project object in its standard tier. We assess whether to migrate Projects as a custom object (requires Pipedrive Advanced tier or above for full custom object support) or as a set of linked Activities and Notes with a project identifier tag. The customer selects the strategy during scoping.

Wice Tasks linked to contacts or deals migrate as Pipedrive Activities. Tasks nested inside Projects are exported with their parent Project context preserved (as a custom field or activity note) so the hierarchy can be reconstructed in Pipedrive if the customer opts for the custom object Project migration strategy. Orphaned tasks (no contact, deal, or project link) are flagged for customer review before import.

Wice differentiates basic and advanced campaigns with targeting and tracking properties. Pipedrive does not have a native campaign object. Basic campaign metadata (name, start/end date, type) migrates as a Note on the relevant Deals or Organizations with a 'Campaign' label. Campaign targeting lists do not map to Pipedrive lists because Pipedrive lists are contact-segmentation tools for email sequences, not campaign audience repositories. We document the campaign structure for rebuild in an email marketing tool.

Wice Tickets (support tickets linked to contacts or organizations) have no direct Pipedrive equivalent in the sales CRM. We migrate ticket metadata (subject, status, priority, description) as a Note on the relevant Organization or Person, or we flag the ticket count for migration to a dedicated helpdesk tool (Zendesk, Freshdesk) if the customer chooses to split support and sales tools. Ticket numbering sequences will reset in Pipedrive.

Wice free-text Notes attached to contacts, organizations, deals, or projects migrate to Pipedrive Notes. The note body transfers as plain text with the original Wice attachment date preserved. Formatting (bold, lists, inline images) may be simplified depending on the destination field; we flag any notes with complex formatting for manual review post-migration.

Wice Gold-tier custom fields on contacts, organizations, deals, and projects map to Pipedrive custom fields. We create each custom field in Pipedrive (with matching type: text, number, date, dropdown, checkbox) before importing any records. Any picklist-style custom fields require a value-translation step if the Wice picklist values differ from the Pipedrive field options. We document every picklist value with its mapping during discovery.

Wice uses a category system for deduplication and record classification. Categories do not map 1:1 to Pipedrive Labels because Pipedrive Labels are free-form per-record tags rather than structured classification tiers. We export Wice category assignments as a custom field (comma-separated or multi-select if Pipedrive supports it for the target field type) so the customer retains the classification data and can reclassify as Labels post-migration if desired.

Wice Owner references on Contact, Organization, Deal, and Project records resolve by email match against the Pipedrive User table. Owners without a matching Pipedrive User go to a reconciliation queue. The customer provisions any missing Users in Pipedrive before the record import phase begins. Inactive Wice users are migrated as inactive Pipedrive Users with a note indicating the original Wice status.