Migrate from Patent Hive to Twenty CRM

Patent Hive Person records map directly to Twenty CRM People. First name, last name, email, phone, and job title transfer as standard fields. The original create date is preserved in a custom datetime field because Twenty sets CreatedAt at migration time. Owner resolution matches Patent Hive user IDs to Twenty workspace members by email.

Patent Hive stores the linked Organization as an ID on the Person record. During migration, the Organization must land in Twenty Company first so the companyId foreign key resolves. Persons without a primary Organization are linked to a placeholder 'Unassigned' Company record.

Patent Hive Organization maps to Twenty CRM Company. Company name, domain (website URL), industry classification, and employee count transfer as standard fields. Industry values are mapped through a pick-list alignment since Patent Hive and Twenty use different standardized taxonomy, and ensures consistency across reporting views.

Patent Hive Deal maps to Twenty CRM Opportunity. Deal name, amount, and close date transfer directly. Deal stage maps through a value-mapping table since Twenty Opportunity Stage is a pick-list. Owner assignment is resolved by email match to Twenty workspace members before the Opportunity is created.

Patent Hive deal owner is stored as a user ID. Twenty CRM Opportunity links owners through workspace membership. The migration resolves each owner ID to the corresponding Twenty member by email. Unresolved owners are flagged and assigned to a fallback workspace member for migration continuity.

Patent Hive activity records with type 'call' or 'meeting' map to Twenty CRM Task. Subject line transfers as the Task title, due date is preserved if set, completion status maps from the Patent Hive activity status flag, and original timestamps are kept for audit continuity.

Patent Hive notes map directly to Twenty CRM Notes. Note title becomes the Note subject, body content transfers as the Note body text. Notes attached to specific Persons or Organizations link to the corresponding Twenty People or Company record after those records are created.

Patent Hive custom fields on any object require manual pre-creation in Twenty Settings → Data Model before the migration runs. FlitStack delivers a custom-field creation checklist as part of the migration plan so workspace setup is complete before data validation begins.

Patent Hive custom objects map 1:1 to Twenty CRM custom objects. Custom-object relationships that use Patent Hive's N:N model require a junction object in Twenty when the relationship is many-to-many. FlitStack surfaces these as part of the pre-migration mapping document.

Patent Hive user records map to Twenty workspace members. Resolution is by email match — the Patent Hive user email is matched against the Twenty member list. Users not yet invited to Twenty are flagged before migration so the team can pre-invite them or assign records to a fallback owner.