Migrate from XMPie to Pipedrive

XMPie contact records extracted from the SQL database map directly to Pipedrive person records. Name, email address, phone number, and mailing address transfer as standard person fields. Where a recipient has no email address, the person record is created with available contact data and flagged for manual enrichment review.

XMPie stores company affiliation as a free-text field on the recipient record. We split this out: a matching Pipedrive organization is created for each distinct company name, and the person record is linked via the organization_id field. Unmatched company names create individual organizations named from the field value.

XMPie campaigns have no direct Pipedrive equivalent — they are communications programs, not sales opportunities. We merge each XMPie campaign run into a Pipedrive deal: the campaign name becomes the deal name, the campaign-run total ordered quantity becomes the deal value, and campaign-run status maps to a Pipedrive pipeline stage. Multiple campaign runs for the same product can be rolled into a single deal or kept separate based on the client's reporting requirements.

XMPie campaign-run statuses (e.g., Draft, Scheduled, In Production, Completed, Cancelled) map value-by-value to Pipedrive deal stages in the target pipeline. The mapping table is defined during the planning phase; completed runs typically map to a Closed Won or Completed stage in Pipedrive while cancelled runs map to Closed Lost.

XMPie products exported from the uStore database map to Pipedrive products directly: product name, SKU (catalog number as code), price, and unit name transfer as-is. Products are migrated first so that deal records can link to them via the deal_products table during the deal migration phase.

Each unique column header from the XMPie recipient data export — demographics, preferences, segment tags, and campaign-specific fields — becomes a Pipedrive custom field on the person record. Pipedrive creates these fields using POST /personFields and returns a hash key per field; FlitStack stores the XMPie column name to Pipedrive hash mapping in the migration workbook for the full run.

XMPie audience segments are defined by parameter rules per campaign (segment name + color-coded precedence). We extract the final segment assignment per recipient as of the last campaign run and write it as a Pipedrive label (tag) on the person record. The segment precedence order is preserved as a note on the label for reference during Pipedrive segmentation.

XMPie records the scheduled date, start time, and completion timestamp for each campaign run. These transfer as custom datetime fields on the Pipedrive deal record (e.g., Campaign_Scheduled_Date__c, Campaign_Completed_Date__c) so that deal timelines can reference the original communication schedule without overwriting Pipedrive's native close date.

Free-text notes attached to a campaign in XMPie Circle are extracted and written as Pipedrive notes on the corresponding deal record. The note header references the original XMPie campaign ID and field label so admins can trace the origin after migration.

XMPie stores design packages (.dpkg), personalized PDFs, and variable image assets as server-side files. Pipedrive can store file attachments on records but is not a digital asset management (DAM) system. We flag all file attachment records in a skip file and provide a download manifest so the client's team can host assets externally and link to them from Pipedrive notes.