Migrate from Market Maker to Twenty CRM

Market Maker contact records map directly to Twenty's People object. All standard contact properties (name, email, phone, job title) transfer as direct field mappings. People records must be imported after Companies because the companyId relation requires the target company record to exist first.

Market Maker stores the primary company as a property on the contact record. During migration, we extract this value and write it as a companyId lookup field on the Twenty People record. Contacts without a primary company receive a placeholder company record or import as standalone People without a companyId.

Market Maker account records map directly to Twenty's Companies object. All core company attributes including company name, domain/website URL, industry classification, employee headcount, and annual revenue figures transfer via direct field mapping. Companies must be imported first in the migration sequence because both People and Opportunities objects reference them through lookup fields. The import order constraint is enforced by Twenty's referential integrity requirements.

Market Maker parent-child account hierarchies map to Twenty's parentId field on Company records, preserving the organizational hierarchy during migration. Parent companies must be imported before child companies to correctly resolve the foreign key relationship. Our migration process includes circular reference detection that flags any orphaned parent links or recursive hierarchy loops before the migration commits, preventing data integrity issues in Twenty's company structure.

Market Maker deal records migrate to Twenty's Opportunities object. Deal name, amount, expected close date, and stage/status fields map directly. Opportunities must be imported after Companies and People because they link to both via companyId and personId (or contactId) lookups.

Market Maker pipeline stages map to Twenty's stage select field. Each stage name from Market Maker requires explicit mapping to a corresponding Twenty stage option. If Market Maker has more stages than Twenty's default set, we create custom stage options in Twenty's data model before migration runs.

Market Maker activity records (logged calls, emails, meetings) migrate as Twenty Tasks. Each Task preserves its original completion date, description/body text, and owner assignment via the assigneeId relation. Task type is set based on the source activity type (call, email, meeting) for filtering in Twenty's UI.

Market Maker notes transfer as Twenty Notes attached to the relevant People, Company, or Opportunity record via the noteableId and noteableType fields. Rich-text formatting is preserved where Market Maker's export format supports it. Notes without a parent record attach to the most relevant entity based on context fields in the source export.

Market Maker owner/user references resolve by email match against Twenty Workspace Members. Unmatched owners are flagged before migration — your team either invites them to Twenty first or assigns their records to a fallback member. No record lands without a valid assigneeId in Twenty.

Market Maker custom objects (if present in your plan) map 1:1 to Twenty custom objects. Custom object associations that use N:N relationships in Market Maker require junction objects in Twenty — we document these in the pre-migration schema plan and create the necessary relation fields before import.

File attachments linked in Market Maker records migrate as attachment URLs stored in a custom text field on the relevant Twenty record, or are re-uploaded to Twenty's file storage. Large files may require post-migration manual verification. We document every attachment reference in the migration plan for your team to confirm after cutover.

Market Maker workflows, sequences, and automation rules do not transfer to Twenty. These are platform-native constructs that require manual rebuild in Twenty's workflow builder or via external automation tools. We export your workflow definitions as a structured reference document to guide your admin through the rebuild.