Migrate from Marketing Star to Pipedrive

Marketing Star Contacts map directly to Pipedrive People. The critical validation gate: Marketing Star requires every contact to have either an email address or a mobile phone number; Pipedrive does not enforce this. We run a pre-import validation that flags all records missing both email and phone, then present three paths — exclude, suppress, or enrich with a placeholder. The original Marketing Star contact ID is preserved in a custom field mstar_contact_id__c on the Pipedrive Person for audit trail and source-of-record reconciliation.

Marketing Star does not have a native Organization or Company object; contacts are standalone. Pipedrive People require an Organization link for full relationship tracking. We derive Organizations from contact company names and email domains during migration: for each distinct domain or non-null company_name value in the contact list, we create an Organization record, then link all People with matching domains or company_name values. This step must complete before People import so the Organization IDs are available for resolution.

Marketing Star Lists are the primary segmentation unit with record-per-list caps (50,000 on Essentials, 100,000 on Premier, 500,000 on Ultimate). Pipedrive has no direct equivalent; segmentation is tag-based or filtered static list-based. We export list membership as contact-to-list association rows, then create Pipedrive tags named for each original list (or prefixed to avoid naming conflicts). For lists exceeding the Marketing Star cap that were split into child lists, we recreate the combined segmentation logic as a single tag or a smart list filter using multiple tag conditions.

Marketing Star Campaigns (email, SMS, QR code) have no direct Pipedrive equivalent. Pipedrive does not track campaign send history as a first-class object. We migrate campaign metadata — campaign name, send date, send volume, open rate, click rate — as a custom activity note or a custom text field on the Person record. Campaign attribution (which Person was in which campaign) is preserved as tag membership so the customer can filter People by campaign exposure in Pipedrive.

SMS contacts in Marketing Star are distinguished by a mobile phone number and a mobile opt-in flag. We map the mobile phone to Pipedrive's phone field and the opt-in status to a custom field sms_consent__c (boolean or date depending on available field type). If the SMS opt-in was per-campaign in Marketing Star, we preserve the most recent opt-in status and the campaign context as a tag on the Person record. Calls and SMS activity history migrates as Pipedrive Activities (calls logged as call-type activities, SMS logs as notes or custom activities).

Marketing Star Forms capture leads and populate contact fields. Form structure (field names, required flags, conditional logic) does not migrate to Pipedrive because Pipedrive does not have a native form builder in the base CRM (LeadBooster add-on provides chatbot and form capture separately). We migrate form submission data — the contact records and their field values — as Person properties. Form field names map to Pipedrive Person custom fields; we pre-create those fields in Pipedrive before the Person import so the mapping is satisfied at insertion time.

Marketing Star does not have a native deal or opportunity object, but teams transitioning to Pipedrive often create Deals manually during or after migration to begin using Pipedrive's pipeline. We do not create Deals from Marketing Star records unless the customer has a custom Deals equivalent (e.g., a spreadsheet export of sales opportunities). If provided, Deal name maps to title, Deal value maps to value, Deal stage maps to Pipeline stage, and owner resolves via email lookup against Pipedrive Users. Close date maps to expected_close_date.

Marketing Star engagement history (calls, emails, meetings, tasks) maps to Pipedrive Activities. Call engagements become Pipedrive Activities with type = call; emails become type = email or note depending on content; meetings become type = meeting; tasks become type = task. Each Activity is linked to the parent Person (Who ID) and, where applicable, the Organization (Org ID) or Deal (Deal ID). Activity timestamps preserve the original Marketing Star engagement date for timeline ordering. Notes migrate as Pipedrive Notes attached to the Person record.

Marketing Star contact custom properties (beyond the standard fields) map to Pipedrive Person custom fields. We pre-create all destination custom fields in Pipedrive before any Person records are inserted, using the closest matching Pipedrive field type: text for strings, numeric for integers or decimals, date for date values, drop-down for picklist-equivalent values. Multi-select or multi-checkbox properties in Marketing Star become Pipedrive multi-select fields or tags depending on the customer's preference during scoping.

Marketing Star Automation Workflows — trigger-based sequences of email, SMS, and action steps — do not migrate to Pipedrive. The two platforms use different automation models with no direct equivalent. We deliver a written inventory of every active Marketing Star Workflow: trigger type, conditions, sequence of actions, and estimated Pipedrive workflow replacement (manual activity creation, automated workflow rules, or a third-party sales engagement tool). The customer's admin or a Pipedrive-certified consultant rebuilds these post-migration.