Migrate from Black Ice CRM to Pipedrive

Black Ice CRM Accounts map directly to Pipedrive Organizations. We extract company name, address fields, phone, website, and any custom fields from the Black Ice Accounts module. The Organization is created first during migration to serve as the parent for any linked Contact records. Company dedupe uses name and domain matching to prevent duplicates on import. Black Ice Accounts with no associated Contacts are migrated as standalone Organizations.

Black Ice CRM Contacts map to Pipedrive People. Each Contact carries individual fields including name, email, phone, role/title, and custom properties. The contact-to-account relationship migrates by resolving the Black Ice Account name or ID as the Organization reference on the Pipedrive Person. Any Contact without a matching Black Ice Account is imported first and linked manually or via a post-import dedupe pass.

Black Ice CRM Potential Tracking objects map to Pipedrive Deals. The Potential stage name becomes the Pipedrive Deal stage label, and the estimated value maps to the Deal value field. We extract all stage names from Black Ice during the schema audit and configure a matching Pipedrive pipeline before migration. If Black Ice has multiple pipeline objects, each becomes a separate Pipedrive pipeline (available on Advanced and above) or a separate Deal category within a single pipeline.

Black Ice CRM Leads map to Pipedrive Leads if the customer's Pipedrive account has the Lead feature enabled, or to People if Leads are not active. We confirm the customer's Pipedrive configuration during scoping. Lead status and source information migrate as custom fields or standard Pipedrive fields depending on availability in the destination account tier.

Black Ice CRM Quotes contain header fields (customer reference, quote date, validity period) and line items tied to the product catalog. We split Quotes into a Pipedrive Deal (header fields as Deal fields and notes) with Product items added as Deal Product entries. Quote PDF attachments migrate as Deal attachments. If Pipedrive's Advanced or higher tier is in use, the Deal carries the line item total as the Deal value with individual products listed in the Products section.

Black Ice CRM Orders are derived from accepted Quotes and trigger automatic stock reduction. We map Order records to Pipedrive Deals marked as Won at the appropriate stage, preserving order number, date, total value, and line items. The Black Ice order-to-invoice relationship is recorded as a Deal note or activity entry in Pipedrive because Pipedrive has no native Order object. Stock reduction logic does not migrate; the customer's admin sets up manual stock reconciliation or an integrated inventory add-on post-migration.

Black Ice CRM Invoices link to Orders and carry payment status, due date, and line item data. Pipedrive does not have a native Invoice object. We migrate invoice records as Pipedrive Deal notes with key fields (invoice number, date, amount, status) in structured text, and the invoice PDF as a Deal attachment. For customers requiring invoice generation in Pipedrive, we document this as a gap and recommend Pipedrive's integrated billing partners (Xero, Harvest, or a custom integration) as a post-migration step.

Black Ice CRM Products (name, SKU, price, stock quantity) map to Pipedrive Products. Product code migrates from the Black Ice SKU field. Current stock quantities and reorder thresholds migrate as Pipedrive Product stock fields. However, Pipedrive does not automatically reduce stock on deal stage change, so the customer's admin must configure manual stock reconciliation or a third-party inventory integration post-migration.

Black Ice CRM stock levels and reorder thresholds migrate to Pipedrive Product records as current stock quantity and minimum stock level. Live inventory updates that occur in Black Ice during the migration window are reconciled post-migration. We flag that picking lists and automated stock alerts in Black Ice are application-generated derived data and do not migrate as records; the current stock snapshot is the deliverable.

Black Ice CRM's fully customisable modules mean custom fields vary by deployment. We require a pre-migration field audit via sample export or screen walkthrough to document the actual schema before building the mapping. Custom fields map to Pipedrive custom fields using the closest available field type (text, number, date, picklist, checkbox). Pipedrive field type constraints may require a picklist migration to a multi-select text field if the destination field type does not support the source format.

Black Ice CRM Users (assigned to Accounts, Contacts, Deals) map to Pipedrive Users. We resolve by email address match. Any Black Ice User without a matching Pipedrive User goes to a reconciliation queue for the customer's admin to provision before record import. Inactive Black Ice users are optionally migrated as inactive Pipedrive users to preserve assignment history.

Black Ice CRM activity records (calls logged against Contacts or Deals, tasks assigned) map to Pipedrive Activities. Call disposition and duration migrate as activity details or custom fields. Meeting records map to Pipedrive Activity with type Meeting. Activity timestamps preserve the original Black Ice creation date. Black Ice note records map to Pipedrive Notes on the parent record. If Black Ice exposes engagement history via export, we map it to Pipedrive Activities in the same dependency order as the parent record.