Migrate from Goodlegal to Twenty CRM

GoodLegal contacts map directly to Twenty People. Twenty does not split leads and contacts into separate objects the way Salesforce does — all individuals land in the same People object. Email is the unique identifier used for relation linking during CSV import. Phone, job title, address, and custom fields carry over as-is.

GoodLegal companies map to Twenty Companies. Address fields in GoodLegal (street, city, state, postal code, country) need to be mapped into Twenty's flat address structure. Parent-child company hierarchies in GoodLegal map to Twenty's parentCompanyId relation field. Multi-company contacts (N:N in GoodLegal) collapse to one primary companyId with additional companies noted in a custom field.

GoodLegal matters map to Twenty Opportunities. The matter name becomes the Opportunity name, the estimated value becomes amount, and the close date maps to opportunitytiming. Stage names (Intake, Active, Closed) are stored in a custom select field since Twenty's native stageName is designed for sales pipelines. Original stage values are preserved as a custom field for reporting continuity.

GoodLegal matter stage names have no native equivalent in Twenty CRM. We create a custom select field (Stage__c) on the Opportunity object before import and populate it with the exact stage values from GoodLegal. Stage-enter timestamps are stored as custom datetime fields for timeline reporting.

GoodLegal call and email activities map to Twenty Tasks. The activity type (call vs. email) is stored in a custom select field (Activity_Type__c) since Twenty Tasks do not have a native type discriminator. Original timestamps, owners, and body content are preserved. Tasks are linked to the parent People record via relation.

GoodLegal meetings map to Twenty Events. Start and end times are preserved as eventDate and endDate. GoodLegal records meeting titles and attendees but not duration — duration is computed from the start/end delta after migration. Attendee relationships are stored in a custom text field listing attendee emails.

GoodLegal notes migrate to Twenty Notes with the original body content preserved. Rich-text formatting is retained where possible. Notes linked to specific records carry the same relation in Twenty. Any note-level attachments are handled separately as file imports. The migration preserves note creation timestamps as custom datetime fields for audit trail continuity.

Fields like matter_type, billing_arrangement, client_status, practice_area, and referral_source have no native equivalent in Twenty. These are created as custom fields in Settings → Data Model before data import. Select-type custom fields need their pick-list values manually configured in Twenty after migration — the mapping plan documents every value transition.

GoodLegal document templates have no direct counterpart in Twenty CRM. Templates are exported as Notes with a custom boolean field (Is_Template__c = true) and the template content stored in the body. The rebuild plan references these tagged Notes so your team can reconstruct templates in Twenty's workflow engine.

GoodLegal file attachments are downloaded and re-uploaded to Twenty's file storage. Files are associated with the parent record (People, Companies, or Opportunities) using Twenty's relation linking. Any GoodLegal-specific file metadata is stored in a custom text field on the Note attached to the file record.

GoodLegal owner and user records map to Twenty Workspace Members. Resolution happens via email match — each GoodLegal user email is matched to a Twenty member by email. Unmatched owners are flagged before migration so your team can create the corresponding Twenty user first. This prevents orphaned records with unresolved owner relations.

GoodLegal supports N:N relationships between contacts and companies. Twenty's CSV import sets one primary companyId per People record. Secondary company relationships are preserved in a custom text field listing additional company IDs or names. Full N:N reconstruction via the UI is recommended after migration for data completeness.