Migrate from Livespace CRM to Twenty CRM

Livespace Person records map directly to Twenty People. Standard fields (name, email, phone, address) map 1:1 to Twenty's name, email, phoneNumber, and address fields. Custom Person fields discovered via the Get custom fields endpoint are pre-created in Twenty Settings → Data Model before import as text, number, date, or select fields depending on type. The Livespace lifecycle stage and source attribution are mapped as custom fields on People because Twenty does not ship a native lifecycle property.

Livespace Companies map 1:1 to Twenty Companies. The domain name from Livespace's company record populates Twenty's domainName field. Company-to-Person associations (person-to-company links in Livespace) are resolved by matching the Livespace company_id on each Person record and creating the corresponding workspaceOrganizationLink in Twenty after the Company batch is committed.

Livespace Deals map to Twenty Opportunities. The deal name, value, stage, owner, expected close date, and created/modified timestamps transfer directly. Livespace's deal custom fields (pipeline-specific additional fields) are pre-created in Twenty's Opportunity object as custom fields. Deal probability can be mapped as a custom field since Twenty does not expose per-stage probability percentages by default. Closed-Lost and Closed-Won statuses map to Twenty's stage values.

Livespace Spaces define separate working environments or sales pipelines within a single account. Twenty uses a single Opportunity pipeline with stage values rather than separate Spaces. We flatten multiple Spaces into a single Twenty pipeline with stage values named to reflect the customer's process. If the customer needs Space separation at the reporting level, we document it as a grouping tag on Opportunities. Space-level deal counts are preserved in a custom field on each Opportunity.

Livespace Tasks (assignable work items linked to Deals or Persons) map to Twenty Tasks with title, body, status, dueDate, and assignee preserved. Task assignment in Twenty uses the assigneeId field which we resolve via email match against the Twenty workspace Member list. Completed versus open task states transfer as-is. Tasks linked to Deals resolve to the corresponding Opportunity record in Twenty.

Livespace Users map to Twenty Members. We resolve by email address, which is the primary identifier in Twenty's invitation and member management system. Members must exist in Twenty before importing any record with an owner reference, per Twenty's documentation. Any Livespace User without a matching Member invitation goes to a reconciliation queue for the customer's admin to provision.

Livespace Teams group Users and can be assigned as deal owners. Twenty does not ship a native Team object with its own permissions model. We flatten team memberships into individual Member assignments and record the original team membership as a custom picklist field on each Member record. If the customer uses Teams for reporting grouping, we create a Team custom field on People and Opportunity.

Livespace custom fields on Persons, Companies, and Deals are discovered via the Get custom fields endpoint at the start of every migration run. Each custom field is pre-created in Twenty Settings → Data Model before any record import begins. Field types are mapped: Livespace text to Twenty text, date to date, picklist to select, multi-select to multi-select. Picklist values are copied verbatim. Required and hidden field flags are configured in Twenty's field settings. Date formats are normalized to ISO 8601 for Twenty's ingestion.

Livespace Contact Groups are static segment lists exposed via the Get contact group list endpoint. We export group memberships and create a custom multi-select picklist field on the People object in Twenty named segment or list membership. Each Person record receives the applicable segment values. Dynamic groups (if the customer uses Livespace's dynamic segmentation) are documented in the written handoff as a filter definition for manual rebuild in Twenty or a third-party segmentation tool.

Livespace Sources track where leads originated (web form, referral, event, cold outreach, etc.) and are exposed via a dedicated source list API. Twenty has no native source attribution object. We map source values as a custom select field named lead_source on the People object in Twenty, populating the value from Livespace's source field on each Person record. This preserves attribution data without schema modification at the account level.

Livespace email sequences (multi-step outbound campaigns tied to Persons or Deals) have no public API endpoint in Livespace. Sequence membership, step status, timing rules, and cadence definitions cannot be read or migrated programmatically. We document all sequences in a written summary including step count, delay between steps, subject line, and associated Person segments. The customer's admin rebuilds sequences in Twenty or a dedicated sales engagement platform post-migration.

Livespace stores Deal and Person attachments in its application layer but the public REST API exposes no attachment download endpoint. Files must be exported manually via the application UI or Livespace's manual export tool before migration begins. We flag this as a required pre-migration manual step in the runbook, provide the customer with a step-by-step download checklist per object, and exclude attachment records from the API-driven migration scope. Files re-uploaded post-migration to the correct Opportunities and People records are a customer-admin task.