Migrate from Smarketing Cloud to Pipedrive

Smarketing Cloud People records map to Pipedrive Person. Standard fields (name, email, phone, lifecycle stage) map directly. Custom properties on People are parsed from the proprietary export format and re-applied as Pipedrive custom fields on Person. We flag any Smarketing Cloud property that has no clear Pipedrive equivalent and present a mapping decision to the customer before import. Person records are imported after Organization records so that the Organization relationship field is resolved at insert time.

Smarketing Cloud Company profiles map to Pipedrive Organization. The relationship table linking People to Companies is exported alongside both objects, and we reconstruct the People-Organization linkage in Pipedrive by matching on Organization ID during the Person import phase. Organization domain becomes the Website field and serves as the dedupe key during import to prevent duplicate Organizations.

Smarketing Cloud Pipeline and its configured stage names are exported in full. Each Smarketing Cloud pipeline becomes a Pipedrive Pipeline, and each stage becomes a Stage within that Pipeline. Stage ordering, probability percentages, and stage names are remapped to Pipedrive stage definitions during schema pre-creation. The customer reviews and approves the stage mapping during scoping before Pipedrive pipelines are provisioned.

Smarketing Cloud Deals map to Pipedrive Deals with the Pipeline and Stage resolved at migration time from the pipeline mapping table. Deal value, close date, owner (resolved via user email mapping), and any custom deal properties migrate as Pipedrive Deal custom fields. Closed-Lost and Closed-Won reason properties from Smarketing Cloud become Pipedrive custom fields on Deal for reporting consistency.

Smarketing Cloud Campaigns with member lists and send history are exported as campaign enrollment records. Each Campaign membership (Contact enrolled, Campaign name, enrollment timestamp, status) migrates as a Pipedrive Activity record of type campaign_enrollment linked to the Person. We use the enrollment timestamp to set Activity date so the campaign history appears in chronological order in Pipedrive's Activity timeline. Campaigns without member lists are documented as Activity categories for manual recreation.

Smarketing Cloud Automation Workflows are not migratable as code because the workflow definition format is not documented and branching logic requires manual review to interpret. We export workflow names, trigger conditions, action sequences, and delay rules as a written inventory document. The customer uses this inventory to rebuild workflows in Pipedrive's Automation tool. Workflow rebuild is outside migration scope and is a separate admin task or paid engagement.

Email Template HTML content and variable placeholders are exported from Smarketing Cloud. Template structure migrates cleanly but variable naming conventions differ between platforms. We remap Smarketing Cloud variable syntax to Pipedrive template variable syntax during the transform phase and deliver a template mapping table showing source template, destination template, and any variables that could not be auto-mapped and require manual correction.

Smarketing Cloud User records (name, email, role, team assignment) export with each object. We map Smarketing Cloud roles to Pipedrive permission sets during scoping. Users are resolved by email match against the destination Pipedrive account's user list. Inactive Smarketing Cloud users are exported with inactive status and held in a reconciliation queue; the customer decides whether to provision inactive users as inactive Pipedrive users or omit them from migration.

Tags applied to People and Companies in Smarketing Cloud are exported as tag strings per record. We apply these as Pipedrive Labels using a bulk apply operation to preserve the tagging structure. Label creation happens before record import so that labels are available at insert time. If a Smarketing Cloud record carries multiple tags, all are applied to the corresponding Pipedrive Person or Organization.

Static lists export as record sets with the list name and member People IDs. We create Pipedrive Static Groups and populate them with the corresponding Person records. Dynamic segments (filter-based lists) are documented with their filter criteria in the workflow inventory. We recommend recreating dynamic segments as Pipedrive filter views rather than exporting them as static groups, since filter logic is not transferable between platforms.

Smarketing Cloud custom objects are exported with schema definitions, field types, and all record data. If the custom object has a simple structure (few fields, no lookup relationships to other objects), we map it to Pipedrive custom fields on Person, Organization, or Deal depending on context. Complex custom objects with multiple fields and inter-object lookups are pre-created as Pipedrive Custom Objects before data import. The customer reviews and approves the custom object mapping strategy during scoping.

File attachments linked to People, Companies, or Activities are exported with their metadata and file URL from Smarketing Cloud. We download files to a staging bucket and re-upload to Pipedrive, preserving the original file name and linking each file to the corresponding Person, Organization, or Activity record in Pipedrive. Files without a resolvable parent record are held in a catch-all bucket for manual review.