Migrate from MiniCRM to Pipedrive

MiniCRM Cards are the primary record container and can hold contact fields, deal fields, notes, tasks, and custom fields simultaneously. During scoping, we audit the customer's card usage to determine which Cards function as Opportunities versus pure contact records. Cards with a deal value, stage, or expected close date map to Pipedrive Deals. Cards used primarily as contact records with no deal data map to Pipedrive People. The split is resolved at migration time using a card-attribute audit, and the mapping rule is documented in the scoping report before extraction begins.

MiniCRM Contact-level fields (name, email, phone, address) map directly to Pipedrive Person fields. Where a MiniCRM Contact is also represented as a Card, we deduplicate by email match to avoid creating both a Person and a Deal-linked Contact. The Person is created first so that the Deal can reference it via the person_id field.

MiniCRM Company records (Firmy) map to Pipedrive Organizations. HubSpot-style company name and available address fields migrate directly. Custom company properties identified during scoping require field-level mapping. Organization is created before any Person import so that the person_id.organization_id lookup is satisfied at Person insert time.

MiniCRM Interests (Interesy) map to Pipedrive Deals where they exist as distinct records separate from Cards. Deal value, expected close date, and stage (mapped from card status or pipeline field) migrate to Pipedrive Deal fields. Stage names require explicit mapping to Pipedrive pipeline stages, which are configured before migration. Deal owner maps via email lookup to the Pipedrive User.

MiniCRM Tasks linked to Cards migrate to Pipedrive Activities. Due date, status, assignee (via email-to-User resolution), and description migrate directly. Task recurrence patterns and reminder settings are noted separately during scoping because they may not map directly to Pipedrive's activity reminder model; we document the gap in the scoping report for admin review.

Free-text Notes attached to MiniCRM Cards migrate as Pipedrive Notes. The association to the parent Card record is preserved by linking the Note to the corresponding Pipedrive Person, Organization, or Deal depending on the split rule applied during migration.

MiniCRM custom fields on Cards (text, number, date, choice types) map to Pipedrive custom fields on the corresponding entity (Person, Organization, or Deal). Choice fields require explicit value mapping — each MiniCRM choice option maps to the Pipedrive option label. We detect all custom fields during scoping, confirm types with the customer, pre-create Pipedrive custom fields via the API before import, and then load values during the record migration phase.

MiniCRM Users (Pracownicy) with name and email map to Pipedrive Users. We resolve by email match against the destination Pipedrive account's User list. Any MiniCRM User without a matching Pipedrive User is held in the owner reconciliation queue for the customer's admin to provision before record migration resumes. Pipedrive does not support user creation via standard bulk import, so we coordinate manual provisioning or API-based user creation outside the migration pipeline.

Calendar events and meeting records associated with MiniCRM Cards migrate to Pipedrive Activities with type Event. Event title, start time, end time, and location migrate directly. Where full attendee lists are available in the MiniCRM export, we map them to Pipedrive ActivityParticipants; if attendee data is not exposed in the export, we migrate the event header and note the attendee gap in the scoping report.

File attachments stored against MiniCRM Cards are migrated where the export exposes them. We flag any attachment size limits during scoping (Pipedrive's file size limit applies). In practice, we migrate attachment references as URL links in a Pipedrive custom field, with a note in the scoping report recommending the customer evaluate Pipedrive's Google Drive or Dropbox integrations for long-term file management post-migration.

Tags applied to MiniCRM Cards for segmentation migrate as Pipedrive Tags on the corresponding record. We deduplicate tags during import to avoid recreating a messy taxonomy in Pipedrive. The customer confirms during scoping whether the existing tag set should be pruned, kept as-is, or rebuilt from scratch in Pipedrive's tag management interface.