Migrate from WORKetc to Pipedrive

WORKetc Contacts map directly to Pipedrive Person records. Name, email, phone, address, and lifecycle information transfer as standard fields. The WORKetc contact owner (a User reference) maps to the Pipedrive Owner ID via email match. WORKetc's lifecycle stage property (if present) migrates as a custom field for segmentation use in Pipedrive.

WORKetc Company records map to Pipedrive Organization. The Organization becomes the parent entity for linked Person records. We preserve Company → Contact relationships by setting the Organization ID on each Person during import. Company-level custom fields migrate to Organization custom fields created before the import phase.

WORKetc Lead records (early-stage prospects with status, source, and conversion flags) map to Pipedrive Lead. The lead status field maps to Pipedrive's Lead Status values. Leads that have been converted in WORKetc (indicated by a converted-flagged record) are routed to Pipedrive as Person records linked to Organizations to avoid creating duplicate Person records in Pipedrive's separate People and Leads data model.

WORKetc Deals (linked to Companies and Contacts with stage, amount, and probability) map to Pipedrive Deals. The WORKetc deal stage maps to a Pipedrive Pipeline Stage. We pre-create the Pipedrive pipeline and stages during schema setup to match WORKetc's deal stages before import begins. Deal amount and probability migrate directly; probability maps from WORKetc's weighted percentage to Pipedrive's stage-level numeric value.

WORKetc Projects with Types and Stages carry non-linear weighted progress that has no direct Pipedrive equivalent. Pipedrive has no native project management object. We offer two strategies during scoping: (1) migrate Projects as Pipedrive Custom Objects with stage weights preserved as custom fields and progress mapped to a numeric value; (2) link Projects to Deals as linked records using Deal-linked custom fields. Strategy selection depends on whether the customer plans to use Pipedrive's Custom Objects module. Milestones and tasks within Projects migrate as Custom Object line items or as linked activity notes.

WORKetc Tickets (linked to Customers, Companies, and Projects with status, priority, and conversation threads) do not have a direct Pipedrive equivalent. Pipedrive has no native case management. We recommend migrating active Tickets as Pipedrive Leads (for new/in-progress) or as Deal-linked activities with a custom Ticket Status field for tracking. Conversation threads migrate as Notes linked to the parent record. If the customer requires Service Cloud-level case management, Pipedrive's native ticketing is not sufficient and a separate service desk integration is needed.

WORKetc Invoice records (line items, totals, payment status linked to Customers and Projects) do not migrate to Pipedrive. Pipedrive has no native billing or invoicing module. We export invoice headers and line item metadata as a CSV reference file for the customer's finance team to re-enter or import into a dedicated billing tool (Stripe, Quadon, or QuickBooks integration). Payment history and linked bank transaction records require separate export and are not part of the CRM migration scope.

WORKetc User records (name, email, role, permission level) map to Pipedrive User records by email match. Pipedrive User provisioning is a prerequisite step before any Person, Organization, or Deal import because OwnerId is required on most records. Any WORKetc User without a matching Pipedrive User goes to a reconciliation queue for the customer's admin to provision before record import resumes.

WORKetc Contractor Portal users are a separate identity class with different permission scopes and may lack standard email addresses or login credentials. Pipedrive has no contractor portal concept. We map all Contractor Portal records to Pipedrive Person records with a custom checkbox field 'Is_Contractor__c' set to true. This preserves the contractor distinction without creating Pipedrive User records (which require email-based login). The customer's Pipedrive admin decides whether to include contractors in Pipedrive's activity assignments.

WORKetc custom fields across Contacts, Companies, Deals, and Projects migrate to Pipedrive custom fields of equivalent types. Text fields map to Pipedrive text, date fields to date, dropdowns to drop-down (single select), and multi-checkbox fields to multi-select drop-down. We create Pipedrive custom fields during the schema setup phase before any data import. Field type compatibility is validated during the discovery audit; any unsupported type (e.g., WORKetc-specific field types without a Pipedrive equivalent) is documented as a gap.

WORKetc engagement records (calls, emails, meetings, tasks, notes) linked to Contacts, Companies, Deals, and Projects migrate to Pipedrive Activities on the corresponding Person, Organization, or Deal record. Each activity type maps to its Pipedrive activity type: Call to Call, Email to Email, Meeting to Meeting, Note to Note, and Task to Task. The original timestamp migrates as the Pipedrive Activity date to preserve timeline ordering. Note body migrates as a Note activity linked to the parent record.