Migrate from Genoo to Twenty CRM

Genoo Leads map directly to Twenty's People object. We extract all standard lead fields (name, email, phone, company, source, status) from Genoo's manual export. During migration, we resolve the email address as the dedupe key and flag any duplicate email records for the customer to reconcile before final insert. Custom lead properties in Genoo become Twenty custom fields on the People object, pre-created via Twenty's metadata API before the import batch runs.

Genoo Contacts (populated through landing page captures and imported lists) map to Twenty's People object using email as the dedupe key. Where Genoo and the destination both have records for the same email address, we use a source-system flag to identify the newer record and update rather than duplicate. Any contact records without an email address are held in a reconciliation queue because Twenty's People object requires an email for the primary key resolution.

Genoo Account records map to Twenty's Company object. Genoo's Account fields are limited (company name, website, industry), so we map these to the corresponding Twenty Company fields. The domain name extracted from the email address on associated Leads and Contacts populates the Company website field where Genoo's Account record does not have one. Company is loaded before People so that the People-to-Company lookup is satisfied at insert time.

Genoo Opportunities are not first-class objects — they are derived from CRM sync where the destination CRM owns the Opportunity. If the customer used Salesforce sync from Genoo, Opportunities were created in Salesforce, not Genoo. We import any Opportunity-like data the customer exported from Genoo as a CSV as a custom object in Twenty or as Opportunity records if the customer has defined an Opportunity model. We document the source structure during discovery and confirm the mapping with the customer before migration.

Genoo Campaigns (drip programs and email nurture sequences) map to a Twenty custom object named Campaign. We extract Campaign name, status, start/end dates, associated program steps, and Campaign membership links (which People enrolled in which Campaign and at what date). The Campaign membership table is the critical relationship we reconstruct using email as the join key across separate export batches.

Genoo Campaign membership links — which Lead enrolled in which Campaign, enrollment date, completion status — are stored as a separate table from Campaign records. We export this as a distinct batch, resolve the associated People record by email, and create a Campaign Membership custom object in Twenty with a lookup to People and a lookup to the Campaign custom object. Without this relationship, the migrated Campaign records in Twenty are orphaned enrollments.

Genoo landing pages and microsites are stored as HTML template blobs with form configuration. We extract the page title, URL slug, and form field definitions as structured data into a Twenty custom object. The full rendered HTML cannot be imported as a functional page in Twenty because Twenty has no built-in page builder; we document the page URLs and form structure for the customer's admin to recreate in their chosen CMS or form tool.

Genoo email templates are HTML-based with subject lines and styling. We extract the template body, subject line, and sender configuration as structured text into a Twenty custom object. Modern email builders do not accept raw HTML in the same way Genoo's template model does, so we treat these as reference documents for the customer's admin to rebuild in their chosen email platform (e.g., Klaviyo, Mailchimp, or a transactional email service). We explicitly flag that these are not live email templates post-migration.

Event registrations in Genoo are stored as Activity-type records linked to Leads. We import registration data — event name, registration date, registration status (confirmed, waitlisted, cancelled) — as Task records in Twenty linked to the associated People record. Post-event attendance data (sessions attended, no-shows) is not available in Genoo's export and is documented as a gap requiring manual or webhook-based supplementation.

Genoo Owners (users who own Leads, Contacts, and Campaigns) map to Twenty WorkspaceMembers. We extract distinct owner email addresses from the export batches and match against the Twenty workspace's member list. If a Genoo Owner has no matching Twenty WorkspaceMember, we hold the assignment field blank and flag the record for the customer's admin to assign manually after the relevant users accept their Twenty invitations.