Migrate from Comet Suite to Pipedrive

Comet Suite person records map directly to Pipedrive People. Name, email, phone, and address fields translate field-for-field. The Comet Suite person record's owner assignment resolves to a Pipedrive user by email match before the record inserts. If the email address does not match any Pipedrive user, the record is flagged for manual owner assignment during the post-migration review.

Comet Suite company records map to Pipedrive Organizations. Company name, domain, industry, and employee count map to the equivalent Organization fields. Multi-location companies in Comet Suite collapse to a single Organization with location data preserved in custom fields. All location-specific addresses are stored in custom text fields on the Organization, enabling your team to reference site details without creating separate Organization records.

Comet Suite locations associated with a company become structured custom fields on the target Organization (Site_Name__c, Site_Address__c) rather than separate objects. If Pipedrive's Organization has multiple addresses, the primary address maps to the main address field. Secondary addresses are added to the Organization's addresses array, preserving the full location hierarchy for reporting and routing purposes.

Comet Suite attendance logs have no native Pipedrive equivalent. We transform each log into a Task with Type='Attendance' and the original timestamp preserved in the Task's due_date field. The task subject carries the location name so the record is searchable in Pipedrive.

Field worker records that include client-facing information (name, email, phone) map to Pipedrive People. The worker's Comet Suite user account resolves to a Pipedrive user by email for owner assignment — if no Pipedrive user exists, the record is assigned to a migration fallback owner and flagged.

Comet Suite service records or job tickets that track service outcomes map to Pipedrive Deals. The Deal name derives from the service record title; the Deal value maps from the service fee or billing amount field. Pipeline and stage are set per your Pipedrive pipeline configuration.

Comet Suite service statuses (e.g., Scheduled, In Progress, Completed, Cancelled) map value-by-value to your Pipedrive pipeline stages. We deliver a stage-mapping table before migration so your admin confirms the routing before records land. The mapping also includes any custom statuses you have defined, ensuring every service state translates to the appropriate Pipedrive stage with no orphaned records.

Comet Suite custom properties on person records (e.g., certification_type, shift_preference) require Pipedrive custom fields to be created via the /personFields API endpoint before migration. Custom field keys are Pipedrive-assigned hashes — we create the field definitions in Pipedrive first, then map values during the load.

Comet Suite custom properties on company records (e.g., service_tier, account_manager) map to Pipedrive Organization custom fields created via /organizationFields. We generate the field creation plan from the Comet Suite property list and apply it before the data load. Each custom field's data type (text, number, date, picklist) is matched to the corresponding Pipedrive field type, ensuring values load without type‑conversion errors.

Comet Suite file attachments associated with service records or people do not migrate as native Pipedrive Files. We download each attachment, re-upload to Pipedrive's document storage, and attach it to the relevant Person or Deal record, flagging any files that exceed Pipedrive's size limits.

Comet Suite user accounts are matched to Pipedrive users by email address. Unmatched users are flagged in the pre-migration audit — your team either creates the Pipedrive user first or assigns those records to a designated fallback owner. If a fallback owner is used, we record the original Comet Suite user ID in a custom field so you can reconcile ownership after your Pipedrive user list is complete.