Migrate from Claritysoft to Pipedrive

Claritysoft Contacts map directly to Pipedrive People. The primary name, email, phone, and address fields transfer 1:1. We preserve the Claritysoft Contact owner as the Pipedrive Person owner by email lookup. If Claritysoft stores a secondary phone or mobile number, these map to Pipedrive custom fields created before migration.

Claritysoft Accounts map to Pipedrive Organizations. The Organization is created before any linked People import so that the Organization ID is available as a lookup reference during Person insert. We use the Claritysoft Account name as the Organization name and preserve the Account website and industry classification in custom fields.

Claritysoft Leads map to Pipedrive Leads using the Lead lifecycle stages (New, Contacted, Qualified) as the basis for Pipedrive Lead status. We preserve the Claritysoft Lead score if one exists as a custom field on the Pipedrive Lead. Leads without an assigned owner go to a reconciliation queue for the customer's admin to assign before production migration.

Claritysoft Opportunities map to Pipedrive Deals. Stage name, deal amount, probability, expected close date, and owner transfer directly. We pre-create Pipedrive pipeline stages matching the Claritysoft pipeline stage names and probabilities before Deals import so that stage assignments are valid at insert time.

Each Claritysoft pipeline stage becomes a Pipedrive pipeline stage within the corresponding deal pipeline. Stage probability percentages migrate to Pipedrive stage probability fields. We configure pipeline stages in Pipedrive during the schema design phase before any record data is imported.

Claritysoft Activities (Calls, Meetings, Tasks) map to Pipedrive Activities of the corresponding type. Timestamps, owners, duration, and notes transfer directly. Activities are linked to the parent Person or Organization via the WhoId and OrganizationId fields. We resolve the parent record ID at migration time using a pre-built lookup cache keyed on the Claritysoft record ID.

Claritysoft Documents attached to Contacts, Accounts, or Opportunities migrate as Pipedrive FileAttachments. We extract the file binary and upload to Pipedrive, then link via the Object ID and Object Type fields. Document metadata (filename, upload date, owner) is preserved in Pipedrive's file record. This requires a file extraction step separate from the record data export.

Claritysoft Custom Fields on Contacts, Accounts, Leads, and Opportunities map to Pipedrive custom fields of matching type. Text fields map to text, numeric fields to number, date fields to date, and picklist fields to set fields. We create the Pipedrive custom fields in the destination account before any record import so that field IDs are available for the data load mapping.

Claritysoft Custom Modules do not have a direct Pipedrive equivalent on standard plans. We treat each Custom Module as a set of related custom fields appended to the primary object it references. For example, a Vehicle Custom Module attached to Account becomes Vehicle custom fields on the Organization record. We document the module structure and relationships in the migration scope so the customer understands the data model change.

Claritysoft Users who own records map to Pipedrive Users by email address. We build an email-to-User-ID lookup table during scoping. Any Claritysoft User without a matching Pipedrive User is flagged in the owner reconciliation report and held from migration until the customer's Pipedrive admin provisions the account.