Migrate from SuiteDash to Pipedrive

SuiteDash Contact records map directly to Pipedrive Person records. Standard properties (first name, last name, email, phone, address) map to Pipedrive's Person field names. Custom fields at the Contact scope migrate as Pipedrive Person custom fields. We resolve HubSpot owner references by email against Pipedrive User records and set the Person's OwnerId accordingly. Any Contact without an email address is flagged for manual review since Pipedrive requires an email for Person creation.

SuiteDash Company records map to Pipedrive Organization records. The Company name becomes the Organization name, domain or website maps to the Organization URL, and address fields map directly. We resolve the Organization record before any associated Contact insert to satisfy the lookup relationship. Any SuiteDash Company with no associated Contacts is imported as a standalone Organization record.

SuiteDash Deals map directly to Pipedrive Deal records. Deal title, value, stage name, and probability migrate as-is. We resolve the linked Contact and Company lookups by matching email and company name against the newly imported Pipedrive records. Owner references resolve via email match to Pipedrive User. Closed-won and closed-lost status from SuiteDash maps to Pipedrive Deal status fields.

Each SuiteDash pipeline and its stage definitions (stage name, position order, probability percentage) are exported during discovery. We configure Pipedrive pipeline stages to match the SuiteDash stage names and order before Deal import, and probability percentages are entered manually since SuiteDash does not export them via API. If the customer has multiple pipelines in SuiteDash, we configure multiple Pipedrive pipelines and map each to the correct stage set.

SuiteDash Company Private fields have no equivalent in Pipedrive's data model. Pipedrive does not support field-level visibility restrictions by contact role. We present two options during scoping: map Company Private fields to Organization custom fields as fully visible, or store them as Notes attached to the Organization record. The customer makes the visibility decision before migration begins. This is a critical scoping step; data migrated to the wrong visibility scope cannot be reversed without manual correction.

SuiteDash Staff records carry role assignments and staff-level custom fields. We resolve Staff records by email against Pipedrive User accounts. The customer must provision Pipedrive Users before migration so that Staff-to-User matching resolves correctly. Any Staff record without a matching Pipedrive User is held in a reconciliation queue. Owner references on Deals, Projects, and Tickets resolve via the User lookup.

SuiteDash exports custom field definitions via GET /contact/meta but Company Private, Organization, Staff, Work Request, Project, and Support scoped fields require separate endpoint discovery. We run a full schema audit during discovery covering all scopes, identify any fields that have no Pipedrive equivalent (Company Private visibility, Staff-scoped), and present resolution options per field. Pipedrive custom field types (text, number, date, picklist, multi-select) are mapped from SuiteDash field types during this phase.

Pipedrive has no native Project object. SuiteDash Projects with custom fields and task hierarchies migrate as tagged Deal records (for project-as-sale tracking) or as Organization-level notes with a structured custom field record in Pipedrive. The customer chooses the strategy during scoping. Task hierarchy and parent-child relationships are preserved in the notes structure. Projects that represent ongoing service delivery are often mapped to Pipedrive Deals with a Project tag.

SuiteDash Appointments (scheduling data, associated Contact, status, location) migrate as Pipedrive Activity records with type set to Meeting or Call depending on the scheduling context. Bidirectional calendar sync settings (Google Calendar, Outlook) do not port and require reconfiguration in Pipedrive's calendar integration settings post-migration. Appointment booking page configurations do not migrate; these require manual setup in Pipedrive or a scheduling tool replacement.

Pipedrive is not a ticketing system. SuiteDash Support Tickets with conversation threads and custom fields migrate as Activity notes attached to the related Person or Organization, or as Deals with a Support tag. The customer chooses the strategy during scoping based on whether support ticket history is needed for sales context. Active ticket workflows do not port; these require rebuilding in a dedicated helpdesk tool or Pipedrive's separate Service product.

Pipedrive does not have an invoice object. SuiteDash Invoice records (line items, payment status, Invoice Custom Fields) are documented as a written record for the customer to evaluate a dedicated accounting tool (QuickBooks, FreshBooks, Zoho Invoice) post-migration. Historical paid invoices are typically left in SuiteDash or exported as PDFs rather than loaded into Pipedrive.

SuiteDash Automations reference internal Contact IDs, Company IDs, and Staff IDs that are not stable across a migration. The automation schema is non-portable regardless of whether SuiteDash exposes an export. We produce an Automation Audit Report listing every active automation, its trigger conditions, actions, and intended Pipedrive Workflow equivalent. The customer's Pipedrive admin rebuilds automations using Pipedrive's Workflow builder from Professional tier.

SuiteDash Tags are freeform labels on Contacts and Companies used for segmentation. We export tags as comma-separated values and map them to a Pipedrive multi-select picklist custom field on Person or Organization. The customer chooses which object carries the tag mapping during scoping. Tags used for marketing segmentation are mapped separately from tags used for sales categorization.

SuiteDash Organization-level settings, white-label configurations, role definitions, and billing settings do not have Pipedrive equivalents. White-label client portals require replacement with Pipedrive'sbranded email templates and, if needed, a separate client-facing tool. Role definitions require manual reconfiguration in Pipedrive's User role and permission set settings.

SuiteDash call engagements (duration, disposition, associated Contact) migrate as Pipedrive Activity records with type set to Call. Call metadata (duration, outcome) is stored in custom Activity fields. Activity date is preserved from the SuiteDash engagement timestamp. Owner references resolve via email match to Pipedrive User.

SuiteDash email engagement content migrates as Pipedrive Activity records with type set to Email. Email body and subject migrate to the Activity notes field. We link the Activity to the resolved Person or Organization record via the WhoId reference. Email timestamps are preserved from the SuiteDash engagement record.

SuiteDash meeting engagements migrate as Pipedrive Activity records with type set to Meeting. Meeting details (location, associated Contact, attendee list) migrate to the Activity record. The Activity is linked to the Person or Organization via WhoId. Timestamps and duration are preserved from the SuiteDash record.

SuiteDash note engagements migrate as Pipedrive Activity records with type set as a note. The note content migrates to the Activity notes field and is linked to the Person or Organization. Attachments referenced in the note are flagged for manual upload to Pipedrive as Files attached to the Activity record.