Migrate from Marketing 360 to Pipedrive

Marketing 360 Contact records map directly to Pipedrive Person. The contact's id becomes the external reference field; firstName and lastName map to name fields; email and phone migrate as typed fields. We resolve the contactName composite field and split it into first and last name where the source field is structured. Duplicate detection uses email as the dedupe key; records with matching emails receive a conflict flag for the customer to resolve before final insert.

Marketing 360 exposes a dedicated Custom Fields API with id-value pairs per contact. We extract the full custom field schema during discovery, pre-create matching custom fields in Pipedrive (with equivalent field types: text, number, date, dropdown, checkbox), and preserve all values as first-class fields during migration. Custom field ordering and grouping in Pipedrive is applied after migration during the configuration phase.

Marketing 360 contact tag arrays (with id and tag name) map to Pipedrive Labels. We extract the complete tag taxonomy from the API and apply tag memberships to migrated Persons. Tag-to-label mapping preserves segmentation logic used for contact filtering and marketing audience building. If a Marketing 360 tag has no matching Pipedrive label, we create it during migration.

Marketing 360 stores assignees as username, fullName, and email nested under contact records. We map assignee email to Pipedrive User email for resolution. Any assignee without a matching Pipedrive User is assigned to the migration service account and flagged in the reconciliation report for the customer admin to provision or reassign post-migration.

Marketing 360 uses arbitrary name/id pairs for contact Statuses and Types. We extract the full taxonomy from the API and evaluate whether each maps to Pipedrive's built-in Person type field (customer, company,未知) or requires a custom field. The customer chooses the mapping strategy during scoping, and we apply it as a value map during the transform phase.

Marketing 360 call engagements map to Pipedrive Activity with type = call. We extract call duration, disposition, and timestamp from the engagement record and populate Pipedrive's Activity fields accordingly. Activity ownership resolves via the assignee mapping.

Marketing 360 email engagements map to Pipedrive Activity with type = email. The email subject, body, and timestamp migrate as Activity subject, note, and due date. Email attachments migrate as linked files if accessible via the Marketing 360 media export.

Marketing 360 meeting engagements map to Pipedrive Activity with type = meeting. We preserve start time, duration, location, and attendee list where available. Activity attendees link to Person records resolved by email match.

Marketing 360 task engagements map to Pipedrive Activity with type = task. Status, priority, due date, and completion status migrate directly. Task assignment resolves via the assignee mapping to Pipedrive User.

Marketing 360 note engagements map to Pipedrive Note records attached to the Person. Note content migrates as rich text; note timestamps are preserved as activity dates. Notes without an associated Person receive a flag for manual association post-migration.

The UXi export tool produces XML containing Posts, Pages, Testimonials, and Media. We extract text content, categories, tags, and media references from the XML export and deliver them as structured content files. Layout files, theme configuration, and root-domain media assets are not included in the export and are flagged as a separate rebuild workstream. We do not rebuild the website design on any destination CMS as part of the CRM migration scope.