Migrate from Moskit to Pipedrive

Moskit Contact records map directly to Pipedrive Person. Standard fields (name, email, phone) transfer 1:1. We run a schema-discovery request against Moskit's Contacts endpoint before extraction to capture all active custom field definitions on the Contact object. Custom fields map to Pipedrive Person custom fields by name and type (text, number, date, picklist). Person records import before Deals so that the PersonId lookup on Deal is satisfied at insert time.

Moskit Company records map to Pipedrive Organization. Organization is created before any Person import so that the OrganizationId lookup on Person is resolved at insert. The Company's Brazilian Portuguese field label (e.g., 'Empresas') is preserved in our extraction; we document the original label in the field glossary included in the delivery package. Domain-based dedupe on Organization Name or Website prevents duplicate organizations on re-import.

Moskit Deal records map to Pipedrive Deal. Pipeline stage, monetary value, owner, and expected close date transfer directly. The dealstage property maps to a Pipedrive Pipeline Stage that we configure before migration. If Moskit Deals have a custom close-reason or loss-reason field, we map it to a Pipedrive Deal custom field. Deals are imported after Organizations and before Persons only when Deals reference Persons directly; the typical import order is Organizations first, then Persons, then Deals with resolved PersonId and OrganizationId.

Moskit Projects are deal-anchored sub-records. Pipedrive's Projects module is a paid add-on available on Growth, Premium, and Ultimate plans (not on Lite or Essential). If the customer has an active Pipedrive plan that includes Projects, we migrate Moskit Projects as Pipedrive Projects with the deal reference preserved as a custom field linking back to the migrated Pipedrive Deal. Projects import last because they reference Deals as their parent record; we remap the Moskit deal ID to the destination Pipedrive deal ID in a two-pass transform.

Moskit Activities are a single object type covering tasks, calls, meetings, and notes. We split by Moskit's activity_type property into Pipedrive Activity types: a Moskit activity_type of 'call' becomes a Pipedrive Call activity, 'meeting' becomes a Meeting activity, 'note' becomes a Note, and 'task' (or any other type) becomes a Task activity. Timestamps, owner, and linked Deal or Contact references transfer to the corresponding Pipedrive activity. We preserve the activity ordering by setting the Pipedrive Activity timestamp to the original Moskit timestamp.

Moskit pipeline stages (named in Brazilian Portuguese) map to Pipedrive Pipeline Stages under a new or existing Pipedrive Pipeline that we create before Deal import. Stage order sequence transfers. Stage-level probability percentages, if set in Moskit, map to Pipedrive Stage probability values. We document the full stage name mapping in the migration package.

Moskit Users map to Pipedrive Users. We resolve by email match. Any Moskit User without a matching Pipedrive User in the destination org goes to a reconciliation queue for the customer's Pipedrive admin to provision. Active/inactive status transfers. Owner assignments on Deals, Activities, and Projects resolve to OwnerId via the email-matched User lookup.

Moskit custom properties on Contacts, Companies, Deals, and Activities map to Pipedrive custom fields on the equivalent object. We query each Moskit object type individually (no bulk custom field enumeration endpoint exists) to retrieve its custom field schema before pulling record data. Field types (text, number, date, picklist) map to the closest Pipedrive field type. Picklist values transfer as-is; Brazilian Portuguese picklist labels are preserved in the destination.

Moskit's WhatsApp Business integration stores conversation metadata (timestamps, participant count, message count) linked to Contact records. Full WhatsApp message content lives in WhatsApp's infrastructure and is not accessible via Moskit's API. We migrate the available conversation metadata as a Pipedrive Note attached to the Person record, noting the gap in the scoping report for the customer to decide whether to export WhatsApp data separately through WhatsApp's own data export tools.

Moskit tags stored as multi-checkbox properties on Contacts or Companies migrate to Pipedrive Labels on the Person or Organization record. Labels are a standard Pipedrive feature on all plans. We transform the multi-value tag array into individual Label assignments per record.