Migrate from SuperOffice CRM to Twenty CRM

SuperOffice Contact maps to Twenty Person. Standard fields (name, email, phone, address) map directly. Custom fields from SuperOffice userDefined table migrate as custom fields on Person, which must be pre-created in Settings -> Data Model before import per Twenty's requirements. The Person-Company relationship is established via the workplace link: we create the Company first, then map the Contact's associate link to the workplace relationship on Person during import.

SuperOffice Company maps to Twenty Company with a 1:1 field mapping. Company is imported first in all migrations to satisfy the Company-Person relationship requirement. All standard address fields and any userDefined custom fields on Company are mapped and pre-created in Twenty before import.

SuperOffice Sale maps to Twenty Opportunity. The sale stage maps to Opportunity status; the amount maps to Opportunity amount; the linked Contact (via the associate table) links to the Opportunity via the Person participant. We resolve the Person ID at migration time before Opportunity insert so that the opportunity-person relationship is satisfied on first import.

SuperOffice Quote -> QuoteAlternative -> line items is a three-level hierarchy. Twenty has Opportunity and OpportunityLineItem but no native Quote object. We map the primary QuoteAlternative to the Opportunity as line items (Product2, quantity, unit price). Additional QuoteAlternatives are serialized as JSON and stored in a custom field on the Opportunity, then surfaced in the post-migration handoff document so the admin can recreate them as separate Opportunities if needed.

SuperOffice Project has type and status managed via ProjType and ProjStatus list tables, with links to Contacts and Sales via the associate table. Twenty has no native Project object. We create a Project custom object in Twenty's Data Model with type and status as select fields, preserve the type-status link as custom field configuration, and map project memberships as participant records.

SuperOffice Activities (calls, tasks, appointments) link to Contact or Company via the associate table. We map all activity types to Twenty Task: calls use Task with a call_disposition custom field; appointments use Task with startDate and dueDate fields; standard tasks map directly. Activity timestamps and completion status migrate as-is. Links to Contact and Company are resolved via the Person and Company ID lookup.

SuperOffice Selections are named dynamic lists of Contacts, Companies, or Sales. Twenty has no native Selection or dynamic list object. We export each Selection as a named tag applied to the relevant records: for a Selection of Contacts, we add a custom tag (the Selection name) to each Person record; for a Selection of Sales, we add it to each Opportunity. The admin recreates static versions of Selections in Twenty using filtered table views.

SuperOffice documents stored in the so_arc folder can be exported as binary blobs with metadata. Twenty has no native document archive equivalent. We export documents as a structured file share (ZIP organized by record type and ID) with a manifest CSV mapping each file to its SuperOffice record. The admin receives the file export and links documents manually or via a file-storage integration.

Custom fields on Contacts, Companies, Sales, and Projects from SuperOffice's userDefined table are mapped individually to Twenty custom fields. Dropdown lists (UDList definitions) must be recreated in Twenty's Data Model as select options before import. We flag any unsupported field types (for example, SuperOffice's URL fields become text fields in Twenty) and document the transformation.

SuperOffice Users have email, name, and license status. We resolve Users by email match against Twenty Members. The customer must invite all Members and confirm they have accepted before we begin record import, because OwnerId and assignee references on Opportunities and Tasks require a resolved Member ID. Inactive SuperOffice users are mapped to inactive Members or excluded per customer direction.

SuperOffice tags applied across Contact, Company, Sale, and Project objects are exported and mapped to Twenty Tags. Tags in Twenty are a native field type on Person and Company and can be used for filtering in table views.

SuperOffice pipeline stages are tied to the SaleType list table with stage names, order, and probability percentages. We export these as a configuration object and apply them as select options on Twenty's Opportunity status field during workspace setup. The customer configures stage probabilities in Twenty's opportunity settings post-migration.