Migrate from myCRMS.com to Pipedrive

myCRMS.com Contact records map to Pipedrive Person. We use email as the primary dedupe key during import. Phone, address, and custom field values transfer to the corresponding Pipedrive Person fields. The HubSpot-source context of Smart Lists maps to Pipedrive saved filters which we document for manual recreation. Person records import after Organization records so that any Person-to-Company link is resolved at insert time.

myCRMS.com Company records map to Pipedrive Organization. Company name is the primary field and domain/whois data from myCRMS.com becomes the Organization's Website field. Organization is loaded first in the migration sequence so that subsequent Person imports can resolve the organization_id reference without a lookup gap.

myCRMS.com Deals map to Pipedrive Deals. The deal title, value, expected close date, and stage data transfer directly. We create Pipedrive stages to match myCRMS.com stage names before migration begins, so that stage_id references resolve on first insert. Owner assignment transfers from myCRMS.com owner_id to Pipedrive user_id via the email-based owner lookup.

Each distinct stage value discovered in myCRMS.com Deals becomes a Pipedrive Stage within the target Pipeline. We set stage order and probability percentages to match the source stage sequence. If myCRMS.com uses a single pipeline, we create one Pipedrive pipeline with those stages; if the audit reveals multiple pipeline groupings, we create multiple Pipedrive pipelines and map Deals accordingly.

myCRMS.com does not expose a named pipeline abstraction in its documented export; deal records carry stage values without a parent pipeline grouping. If the audit reveals distinct deal groupings by product line or business unit, we create corresponding Pipedrive Pipelines and assign Deals during migration. If all Deals share a single grouping, we create one default Pipeline.

myCRMS.com owner assignments on Contact, Company, and Deal records map to Pipedrive Users. We resolve by email match against the destination Pipedrive account's User table. Any owner in myCRMS.com without a matching Pipedrive User is flagged in a reconciliation report before migration begins; the customer admin provisions missing Users in Pipedrive before the record import phase.

myCRMS.com activity timestamps and type data (calls, emails, meetings, tasks where exposed in export) map to Pipedrive Activity records. We create Activities linked to the parent Person, Organization, or Deal via the activity_type field (call, email, meeting, task). The original timestamp from myCRMS.com becomes the due_date on the Pipedrive Activity.

myCRMS.com notes associated with Contacts or Deals migrate to Pipedrive Note records attached to the corresponding Person, Organization, or Deal via the pins array. Content transfers as the note body. We preserve the original creation timestamp for audit ordering.

myCRMS.com task records map to Pipedrive Activity with type=task. Task subject, due date, status, and owner assignment transfer to the corresponding Pipedrive fields. Completed status maps to Pipedrive's done=1; open status maps to done=0.

Any custom field schemas discovered during the myCRMS.com pre-migration audit are created as typed Pipedrive custom fields before the matching records are imported. Text fields become Pipedrive varchar; numeric fields become int or varchar depending on format; date fields become date; picklist-style values become varchar. We document the full custom field mapping table as part of the migration deliverable so the customer admin can verify type decisions before import.

myCRMS.com Smart Lists for contact management are documented as Pipedrive saved filter configurations during the migration handoff. We do not create these programmatically because Pipedrive's filter API operates on the full dataset rather than a named pre-saved view. The customer admin recreates Smart List equivalents as Pipedrive saved filters post-migration using the documented filter criteria.