Migrate from TeamWave to Pipedrive

TeamWave Contact records (name, email, phone, address, lifecycle stage) map to Pipedrive Person. The TeamWave contact_id primary key is preserved in a custom field tw_contact_id__c for audit and cross-reference. Lifecycle stage from TeamWave maps to a Pipedrive custom picklist field tw_lifecycle_stage__c because Pipedrive's native Person object does not have an equivalent lifecycle property at this tier. Email and phone map directly to Pipedrive's email and phone fields.

TeamWave Company records map to Pipedrive Organization. The company_id foreign key from the TeamWave Contact export is used to reconstruct the Person-to-Organization link in Pipedrive by matching the organization_name field on Person import. Website, address, and industry fields map directly. We preserve the original TeamWave company_id in tw_company_id__c on the Organization record.

TeamWave Deals map to Pipedrive Deals with stage, value, owner, expected close date, and deal history preserved. TeamWave's dealstage property maps to Pipedrive's stage_id by name match against the target pipeline's stage list. The owner maps by email resolution against Pipedrive Users. We reconstruct the Deal-to-Person and Deal-to-Organization links using the contact_id and company_id foreign keys embedded in the TeamWave Deal export.

TeamWave Projects (name, description, status, client association, start/end dates) require Pipedrive's Projects add-on, which is included in Growth ($49/seat) and above, and available as an add-on on Essential ($24/seat). If the customer is on Pipedrive Essential without the Projects add-on, we migrate Project records as Organization-linked Deals with a tw_project_name__c custom field and a project status custom picklist, deferring native Project objects until the account is upgraded. Custom project fields map to Pipedrive custom fields on the Project object if the add-on is active.

TeamWave Tasks (assignee, due date, status, priority, linked entity) map to Pipedrive Activity records with type=Task. We reconstruct the project_id link by storing it in a custom field tw_project_id__c on the Activity record since Pipedrive Activities do not natively link to Projects. If Pipedrive Projects add-on is active, we create Project Tasks directly. Assignee resolution uses email matching to Pipedrive Users; unresolved owners are held in a reconciliation queue.

TeamWave User records (name, email, role, department) map to Pipedrive Users. We resolve by email match. Any TeamWave User without a corresponding Pipedrive User goes to a reconciliation queue for the customer's admin to provision before record import. Role and department from TeamWave are stored in custom fields tw_role__c and tw_department__c on the Pipedrive User since Pipedrive does not have a native department field on User.

TeamWave Calendar Events (title, date/time, linked entity, attendees) map to Pipedrive Activity records with type=Event. Start and end timestamps migrate to the Activity's due and duration fields. Linked entity type (Deal, Project, Contact) is preserved via custom fields tw_event_type__c and tw_entity_id__c for reconstruction. Attendees migrate as ActivityParticipant records if the Pipedrive API version supports it, otherwise as comma-separated text in a custom field tw_attendees__c.

TeamWave HR/Employee records (name, role, department) migrate as Pipedrive Person records tagged with a tw_employee_record__c flag set to true. Role and department store in custom fields tw_role__c and tw_department__c on the Person. If the customer uses Pipedrive's Products or Team capabilities, we create a separate Employee object list rather than mixing employee profiles with external Person records; the customer chooses the strategy during scoping.

TeamWave custom fields on Contacts, Deals, Projects, and Tasks are exported alongside the standard export and mapped to Pipedrive custom fields of equivalent type. Pipedrive supports text, number, date, datetime, single-select picklist, multi-select picklist, phone, email, URL, and address custom field types. We create the Pipedrive custom fields in the target account before migration and map the source values during import. Complex custom field logic (formulas, conditional defaults) does not migrate and is documented as a rebuild item for the admin.

TeamWave stores file attachments linked to Contacts, Deals, and Projects but provides no bulk download mechanism. We do not migrate binary attachments. We capture filename, size, linked object type, and linked object ID from the TeamWave export and produce a re-upload manifest listing each attachment with its target Pipedrive record ID and instructions for manual re-upload in Pipedrive's file attachment UI.