Migrate from GENIEE to Twenty CRM

GENIEE SFA/CRM Contacts map to Twenty People records. We extract contacts from the SFA/CRM subsystem with all standard fields (name, email, phone, address) and custom properties. Japanese field labels are translated during scoping using our Japanese-speaking data engineers and machine-assisted translation, with the original Japanese label preserved in a metadata note. Owner assignment maps from GENIEE user_id to Twenty user/Member email lookup.

GENIEE SFA/CRM Account records map to Twenty Companies. The account hierarchy (parent account, subsidiary structure) maps to Twenty's company workspace relationships. Regional and department data using Japanese regional conventions is converted to standard address and industry fields, with the original regional designation stored in a custom field for reference.

GENIEE SFA/CRM Deal pipeline stages map to Twenty Opportunity stages. We preserve the full stage history including closed-lost and closed-won timestamps, stage probability percentages, and deal amounts. The GENIEE pipeline name maps to a Twenty Opportunity workspace or a custom field for multi-pipeline configurations. Win/loss reasons stored as custom fields migrate to custom Opportunity fields.

GENIEE MA Campaign records with UTM parameters, source, medium, and attribution data map to a Twenty Custom Object (Campaign) or are linked to Opportunities via custom fields depending on whether the customer uses campaign attribution reporting. We normalize UTM source and medium into standardized values during the transform step. Campaign members linked to Contacts map to custom Person-to-Campaign relationship records.

GENIEE DSP campaigns (budget, targeting parameters, ad formats, flight dates, bid strategy) do not map to any standard CRM object. We export DSP campaign metadata as a Custom Object named DSP_Campaign in Twenty with fields for campaign_name, budget, targeting_criteria (as JSON), start_date, end_date, and ad_format. Performance metrics (impressions, clicks, bid logs) are exported as a separate Custom Object named DSP_Metrics linked to DSP_Campaign, as these are analytical in nature and not standard CRM data.

SSP publisher inventory data (slot IDs, floor prices, telco/mobile/desktop classification) is exported as a Custom Object named SSP_Inventory in Twenty. This is SSP-specific data that has no equivalent in standard CRM schemas. We preserve the full inventory configuration as a reference dataset in Twenty, noting that it is not linked to Opportunities or Companies in a standard CRM workflow.

GENIEE SFA/CRM user records (name, email, role, team assignment) map to Twenty Members. We resolve by email match. Any GENIEE owner without a matching Twenty user is held in a reconciliation queue for the customer to provision before record import resumes. User active/inactive status is preserved as a Member field.

Files attached to Contacts, Accounts, and Deals in GENIEE SFA/CRM are exported as binary blobs and re-uploaded to Twenty. We preserve original file names, MIME types, and timestamps. File size limits follow GENIEE tenant-specific configuration; we flag any files exceeding Twenty's attachment size limits for manual handling.

GENIEE SFA/CRM custom fields on Contacts are discovered during scoping, and the full custom property list is mapped to Twenty Person custom fields. Field type conversion (text, number, date, picklist) is handled during the transform step. Japanese field labels are documented with English translations. All custom fields must be created in Twenty Settings before import begins, per Twenty migration documentation.

Custom fields on GENIEE SFA/CRM Accounts are mapped to Twenty Company custom fields. The same discovery and type-conversion process applies. Custom field dependencies on other custom fields (conditional visibility or required rules) are documented as a separate configuration note for the customer's admin to implement in Twenty after migration.

Tags and labels on GENIEE Contacts and Companies are exported as arrays and mapped to Twenty's Tag feature. Tag vocabulary is tenant-defined and preserved as-is. Tags used for segmentation purposes are also preserved as Twenty Tags so that sales teams can use existing tagging conventions without re-tagging records manually.

Notes attached to Contacts, Accounts, and Deals in GENIEE SFA/CRM map directly to Twenty Notes. Rich text formatting is preserved where possible. Notes authored in Japanese are migrated with the original text intact, with a language indicator field set to Japanese for filtering purposes.