Migrate from Market Maker to Pipedrive

Market Maker persons map directly to Pipedrive persons. All standard contact fields (name, email, phone, job title) map 1:1. Owners resolve by email match to Pipedrive users. Persons without an organization link land as orphan records in Pipedrive; your admin can assign a default organization post-migration.

Market Maker organizations map to Pipedrive organizations. Domain-based org matching in Market Maker (company.com) maps to Pipedrive's name field. Parent-child org hierarchies in Market Maker map to Pipedrive's parent_org_id field on the organization record. Multi-address orgs: Pipedrive stores a primary address only; secondary addresses migrate as custom fields.

Market Maker deals map to Pipedrive deals. Each Market Maker deal pipeline becomes a Pipedrive Pipeline; stage names within that pipeline become Pipedrive stages ordered by their Market Maker sequence weight. Stage probability values are not stored in Market Maker — they are set per Pipedrive stage post-migration.

Market Maker call records map directly to Pipedrive activities with type=Call. The call duration in seconds, call result (completed, missed, no-answer), and the parent person or deal ID all migrate to the corresponding Pipedrive fields. Original call timestamps from Market Maker are preserved by writing to Pipedrive's due field, maintaining the complete communication history for each contact or deal record.

Market Maker email activities map to Pipedrive activities with type=Email. Subject line, body text (plain text only — HTML stripped), sender and recipient addresses migrate. Pipedrive does not store full email thread headers; the most recent email in a thread is what migrates.

Market Maker tasks and notes transfer to Pipedrive as activities with type=Task. The task subject, body text, due date, and completion status all migrate to their corresponding Pipedrive activity fields. When a Market Maker task has the completed flag set to true, Pipedrive's activity.done field is set to true via the API, marking the task as done in Pipedrive's activity list.

Market Maker product records (SKU, name, unit price) map directly to Pipedrive products. Market Maker cost or margin fields that have no Pipedrive equivalent are stored as custom number fields on the Product object. Product-deal associations (line items on a deal) migrate as Pipedrive deal products.

Market Maker custom fields on persons (beyond name/email/phone) require Pipedrive custom fields to be created first. Pipedrive assigns a hash key to each custom field — that key must be retrieved from the Pipedrive API before migration writes data. Custom field types (text, number, date, picklist) map to Pipedrive's equivalent field types.

Deal-level custom fields in Market Maker (e.g., contract type, renewal date, probability override) become Pipedrive deal custom fields. Pipedrive deal fields are referenced by their hash key. Picklist fields in Market Maker require value mapping if the picklist options differ from Pipedrive's existing field options.

Market Maker user records map to Pipedrive users by email address. FlitStack resolves each Market Maker owner email against Pipedrive user accounts. Unmatched owners are flagged before migration — your team either creates Pipedrive user accounts for them or assigns their records to a fallback owner. System-level or deactivated users default to the migration initiator's account.

File attachments on Market Maker deals and persons re-upload to Pipedrive's Files section. Files attach to the parent record (person, organization, or deal) using Pipedrive's file association API. Pipedrive stores files with a 25MB per-file limit — files exceeding this are flagged and skipped with a record in the error log.

Market Maker automations and workflow rules do not migrate. FlitStack exports workflow definitions as JSON — trigger conditions, action steps, and filter logic are preserved in a machine-readable format your Pipedrive admin uses to rebuild using Pipedrive Automations (Advanced plan and above) and Sequences (Power and above).