Migrate from Smart CRM Online to Pipedrive

Smart CRM Online Contacts map to Pipedrive People. The contact's name, email, phone, and company association migrate as first-class Person fields. We resolve the Company ID reference from the Smart CRM Online export to the corresponding Organization ID in Pipedrive, which we created in the prior Organizations phase. Any Contact without a resolvable Company reference is flagged for manual Organization assignment before deal association begins.

Smart CRM Online Companies map to Pipedrive Organizations. We create all Organizations before importing People to satisfy the Organization ID lookup on the Person record. Company name becomes the Organization name field. Address, domain, and custom fields migrate as Organization custom fields.

Smart CRM Online Deals map to Pipedrive Deals. We resolve the Company ID from the export to the Pipedrive Organization ID and the primary Contact reference to a Pipedrive Person ID at migration time. Deal value, stage, close date, owner (mapped via email to Pipedrive User), and custom properties migrate directly. Pipeline assignment is configured in Pipedrive before migration so that Deal stage names map to the correct pipeline stage values.

Smart CRM Online pipeline stages are extracted from the Deal export and mapped to Pipedrive Pipeline stages. We configure the Pipedrive pipeline in advance with stage names matching the source, probability percentages, and stage order preserved. If Smart CRM Online uses custom stage names (e.g., 'Proposal Sent' vs 'Negotiation'), we create matching Pipedrive stage labels during the discovery phase.

Smart CRM Online call activity logs map to Pipedrive Activity records with the Call subtype. Call duration, disposition, and timestamp migrate to custom Activity fields. We link the Activity to the parent Person and Deal via the Activity's linked_person_id and linked_deal_id fields in the Pipedrive API.

Smart CRM Online email activity logs map to Pipedrive Activity records with the Email subtype. Subject, body content, direction (sent/received), and timestamp migrate. We link each Email Activity to the parent Person and optionally to a Deal if the source export includes deal association metadata.

Smart CRM Online meeting activity logs map to Pipedrive Activity records with the Meeting subtype. Start time, end time, location, and title migrate. Attendee information from the source export is stored as meeting notes in the Activity body since Pipedrive's native Activity model does not expose a separate attendee list for the standard API.

Smart CRM Online task activity logs map to Pipedrive Activity records with the Task subtype. Due date, status, subject, and completion flag migrate. We preserve the original completion date as a custom Activity field for audit trail.

Smart CRM Online Notes attached to Contact or Deal records migrate to Pipedrive Activity records with the Note subtype. Note content, author, and creation timestamp migrate. We link Notes to the correct Person or Deal via the API's linked_person_id and linked_deal_id fields. If the note contains formatting, we preserve it as HTML within the note body.

Smart CRM Online tags on Contacts and Deals migrate to Pipedrive Labels. We extract all unique tag values from the source export, create Pipedrive Labels during the pre-migration phase, and attach label IDs to the relevant Person and Deal records during import. If Smart CRM Online uses tags as a classification system beyond simple labeling (e.g., for segmentation), we discuss with the customer whether Labels or a custom multi-select field is the better Pipedrive equivalent.

Smart CRM Online Owners (deal owners, contact owners) map to Pipedrive Users. We match by email address. Any Owner in the export without a corresponding Pipedrive User is placed in a reconciliation queue, and the customer's Pipedrive admin provisions the User before record import proceeds.

Smart CRM Online custom fields have no public schema, so we identify them during discovery by extracting the full export and comparing field names against the standard Contact, Company, and Deal schemas. Each identified custom field is presented to the customer for explicit mapping to a Pipedrive custom field of the appropriate type (text, number, date, dropdown, checkbox). Pipedrive's Lite plan supports basic custom fields; formula fields and pipeline-specific fields require the Premium plan. We confirm the customer's Pipedrive plan tier before designing the custom field schema.