Migrate from mQuest to Twenty CRM

mQuest contact records map directly to Twenty People. Standard fields (name, email, phone, job title, address) migrate as-is. The source record's original create date is preserved in Original_Create_Date__c since Twenty sets CreatedAt at import time. Owner assignment resolves by email match against Twenty workspace members.

mQuest company records map to Twenty Companies. The name, domain/website, industry, and employee count fields migrate directly. Industry pick-list values require value-by-value mapping where mQuest uses different industry taxonomy than Twenty's defaults. Parent-company relationships in mQuest map to the Parent CompanyId field in Twenty.

mQuest deal records map to Twenty Opportunities. The deal name, amount, and expected close date migrate directly. Pipeline and stage values in mQuest map to the Stage field in Twenty; stage pick-list options are configured in Twenty's workspace settings before migration. Probability values that exist in mQuest migrate as a custom Number field since Twenty does not have a native probability field.

mQuest contact-to-company associations require Companies to be migrated before People so the foreign-key companyId resolves correctly in Twenty. If a mQuest contact has multiple associated companies, we migrate the primary association (most-recently-modified) as the companyId and surface secondary associations as notes for manual review.

mQuest deal-to-contact associations map to Twenty's Opportunities being linked to People records via the opportunities array on People. People must exist before Opportunities can link to them. If a deal in mQuest has multiple associated contacts, all are linked in Twenty after People migration completes.

mQuest notes map to Twenty Notes, which can be attached to People, Companies, Opportunities, and other records. The note body, title, and created timestamp migrate. Rich-text formatting in mQuest notes is flattened to plain text; complex HTML notes are preserved as plain text with an HTML_Preserved__c custom field for admin review.

mQuest tasks and activities map to Twenty Tasks. Title, body, due date, completion status, and assignee migrate. Assignee resolution uses email lookup against Twenty workspace members — users must be invited and accept before migration runs. Completed-at timestamp migrates as Completed_At_Source__c custom field.

mQuest calendar events map to Twenty Events where available in the destination tier, or to Tasks with an Event_Type__c custom field flag. Start time, end time, title, and attendees migrate. Attendee email resolution uses Twenty workspace member lookup.

mQuest custom objects map 1:1 to Twenty custom objects on Professional and Organization tiers. Custom object creation in Twenty must happen in Settings → Data Model before CSV import runs. N:N relationships between custom objects in mQuest require junction objects in Twenty — we surface this in the migration plan and create the junction table structure during schema setup.

Twenty's CSV import does not include file attachments. We download files from mQuest via API, re-upload them to Twenty's storage, and link them to the parent record by ID. Large files that exceed Twenty's size limits are flagged for manual re-upload. Source file URLs are preserved in Attachment_Source_URL__c for reference.

Workflows, sequences, and automation rules in mQuest do not migrate. We export mQuest workflow definitions as structured JSON and a written description for each rule so your Twenty admin can rebuild them in Twenty's workflow builder. Sequences — timed follow-up cadences — are not natively supported in Twenty at all; teams use third-party sequencing tools post-migration.

mQuest owner IDs resolve to Twenty workspace members by email address lookup. Before migration runs, all expected mQuest owners must be invited to the Twenty workspace and accept their invitations — otherwise owner assignment falls back to the admin user and is flagged in the migration report for manual correction.