Migrate from Star CRM to Pipedrive

Star CRM Contact records map directly to Pipedrive Person. Standard fields (name, email, phone, address) transfer 1:1. Custom contact properties are inferred from live discovery during scoping since Star CRM does not publish its schema, and each custom property is mapped to a Pipedrive custom field of matching type (text, numeric, date, or multi-select). We resolve the Person-to-Organization link by matching the Contact's parent company to a Pipedrive Organization by name.

Star CRM Company records map to Pipedrive Organization. Organization is created before Person records to satisfy the OrganizationId lookup on Person. Company name becomes the Organization name, and address fields map to Pipedrive's address subfields. Custom Company properties migrate as Organization-level custom fields with type mapping confirmed during discovery.

Star CRM Deal records map to Pipedrive Deal with the same deal value, title, and stage preserved. Stage names are reconciled during scoping: each Star CRM deal stage is mapped to a Pipedrive pipeline stage name. Deal-to-Contact linking uses the Person and Organization lookups resolved in previous phases. Deal owner assignment maps via email match to Pipedrive User.

Star CRM Activities (calls, emails, meetings, tasks, notes) map to Pipedrive Activity records. Call engagements map with call type, duration, and disposition; email engagements map as Activity with type email; meetings map as Activity with type meeting. Each Activity is linked to its parent Person or Organization via the context_id and context_type fields. Note content migrates as Activity type note with full body text preserved.

Where Star CRM distinguishes Leads from Contacts, we separate them during export and import them into Pipedrive as Lead records. Lead source, status, and any scoring values transfer as custom fields. If the customer prefers to convert Leads to Persons in Pipedrive during the handoff, we document the conversion mapping in the deliverable.

Star CRM pipeline stages are mapped to Pipedrive Pipeline stages. We create a Pipedrive Pipeline during migration setup with stages named to match the source or mapped to the customer's preferred naming convention. Stage probability percentages transfer if Star CRM stores them; otherwise we set defaults and the customer adjusts post-migration.

Star CRM Tags on Contacts or Deals transfer as Pipedrive Labels. Multi-select tags on a single record split into separate Label assignments in Pipedrive. The customer chooses whether to use Pipedrive's built-in Label feature or store tags as a multi-select custom field during scoping.

Star CRM Owner records (name, email, role) map to Pipedrive User. We match by email address. Owners without a matching Pipedrive User are held in a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Star CRM owners can be mapped to inactive Pipedrive users if the customer wants historical assignment preserved.

Star CRM exports attachments as individual files per record with no parent-archive structure. We download all files, build a manifest linking each file to its source record ID and type, and upload files to Pipedrive as Deal or Person attachments with the correct parent reference. This step adds time proportional to file volume; we estimate and quote it separately during scoping.

Custom fields on any Star CRM object (Contact, Company, Deal, Activity) are inferred during live API discovery and mapped to Pipedrive custom fields of the matching type. Pipedrive supports text, numeric, date, address, multi-select, and single-select custom field types. We create the destination custom fields in Pipedrive before migration begins and map each one explicitly during the data transform phase.