Migrate from Amwork to Pipedrive

Amwork Contacts map to Pipedrive's Lead object if they are unqualified prospects or have no associated Deal, and to Contact if they are linked to a Deal or Company. We apply the split using Amwork's lifecycle stage property and the presence of a linked Deal as criteria. The original Amwork lifecycle stage migrates as a custom field lead_source_detail__c on both Lead and Contact for audit continuity.

Amwork Companies map directly to Pipedrive Organizations. The Amwork company domain becomes the Organization's Website field and acts as the dedupe key during import. Organization is created before any Contact import so that the relationship lookup is satisfied at Contact insert time.

Amwork Deals map to Pipedrive Deals with pipeline and stage mapping. Amwork's dealstage property maps to Pipedrive's stage_name, and pipeline assignments map to Pipedrive Activity sets. Any missing stages are pre-created in Pipedrive before deal import so that no stage reassignment is needed post-migration.

Amwork's Deals and Leads section holds unqualified prospects that have no Company association. These map to Pipedrive Leads with the Amwork lead status field mapped to Pipedrive's open, won, and lost status. Leads that have a Company link in Amwork map to Pipedrive Leads with the Organization field populated.

Amwork Projects have no direct Pipedrive equivalent. We migrate project context as linked notes attached to the related Deal or Contact, preserving project name, description, status, and member list as structured note content. For Amwork projects not linked to a Deal, we attach the note to the primary associated Contact or Organization.

Amwork Tasks migrate to Pipedrive Activities of type task. Assignee resolves via email match against Pipedrive Users. Due dates, priorities, and checklist sub-items transfer as activity fields. Parent-child task hierarchies are flattened into a flat activity list under the parent Deal or Contact, with a custom field parent_task__c preserving the hierarchy reference.

Amwork time entries attach to tasks and projects. Pipedrive has no native time-tracking object, so we migrate entries as Pipedrive Notes with the duration, date, description, and billable flag encoded in structured note text. For billable time entries, we also create a linked Activity record to preserve the entry in the timeline.

Amwork custom fields (text, number, date, choice) map to Pipedrive custom field types of matching type. Choice-type fields become Pipedrive enum or set fields. We pre-create Pipedrive custom field definitions via the API before data migration begins so that all field mappings resolve at import time rather than requiring post-migration schema edits.

Amwork Users map to Pipedrive Users by email match. Owner assignments on Deals, Tasks, and Projects resolve to Pipedrive User records. Any Amwork user without a matching Pipedrive User goes to a reconciliation queue for the customer's admin to provision before record import resumes.

Amwork file attachments on tasks and deals migrate as linked URLs or hosted files depending on the destination storage capability. Large attachment batches are chunked and rate-limited against Pipedrive's API to avoid burst-limit violations. Attachments that reference files no longer accessible are flagged in the reconciliation report.

Amwork multi-workspace accounts map to Pipedrive's org-level grouping. Each workspace becomes a note or tag on the imported Deals and Contacts describing the original workspace context. Workspace-specific settings do not transfer and are documented as configuration items for the customer's admin to apply post-migration.