Migrate from mQuest to Pipedrive

mQuest Contact records map directly to Pipedrive Person. Standard fields (name, email, phone, job title) translate 1:1. mQuest contacts with embedded company data generate a Person and a linked Organization in Pipedrive. The primary company is resolved by most-recently-modified date or your specified rule.

mQuest Company becomes Pipedrive Organization. Domain field from mQuest maps to Organization website. Parent-company hierarchy (if present in mQuest) maps to Pipedrive's parent Organization lookup. Multi-company contacts collapse to one primary Organization link with additional organizations surfaced via Organization-Person relationships.

mQuest Deal maps to Pipedrive Deal with a name, value, and close date. The mQuest pipeline name and stage name are resolved separately — pipeline becomes a Pipedrive Pipeline record, and stage becomes a Stage within that pipeline. Stage probability values from mQuest map to Pipedrive probability_weight fields on each stage.

Each mQuest deal pipeline generates one Pipedrive Pipeline entity. Within each pipeline, mQuest stage names become Pipedrive Stage records with a stage_order position and an optional probability_weight. Stage ordering is preserved from mQuest. If mQuest stores stage-entered timestamps, those migrate as custom datetime fields on the Deal.

All mQuest engagement types (call, email, meeting, note) converge into Pipedrive's single Activity object. The activity type string is preserved from mQuest. Original timestamp, owner, and subject line are migrated. Each Activity is linked to its parent Person, Organization, or Deal via the activity's related_object fields.

mQuest custom properties on any object require Pipedrive custom fields to be created before migration. Pipedrive assigns per-account hash keys (e.g. a1b2c3d4e5f6) that are not known until after field creation. We create all custom fields in a pre-migration step, retrieve the generated keys, update our field mapping, then run the migration with correct key references.

If mQuest stores product catalog entries, these map to Pipedrive Product with name, code, unit_price, and description. Products linked to deals via line items require the Product record to exist in Pipedrive before the deal migration runs. If mQuest has no products, this mapping step is skipped.

mQuest file attachments and linked documents are downloaded from source storage and re-uploaded to Pipedrive Files. Files are attached to the parent Person, Organization, or Deal record in Pipedrive. Files exceeding Pipedrive's 25 MB per-file limit are excluded and flagged in the migration report.

mQuest owner IDs are resolved against Pipedrive users by email address match. If a Pipedrive user account does not exist for a given owner email, the record is assigned to the admin user and flagged for review. Owner resolution is validated before migration so no record lands without a recognized owner.

If mQuest maintains a distinct Lead object separate from Contact, those records migrate to Pipedrive's Lead entity rather than Person. Leads inherit all Person fields plus Pipedrive-specific lead fields (lead_status, public_fields_hash). Contacts without a company association and in early pipeline stages may also route to Lead based on your specified routing rules.