Migrate your Livespace CRM data

Persons are the primary contact object in Livespace. Standard fields (name, email, phone, address) are well-documented in the API. We map each Person record including lifecycle-stage and custom fields. Source tracking is available via a dedicated endpoint.

Companies are a separate object that can be linked to Persons. API supports GET/POST operations on the Company endpoint. We preserve company-level data and the person-to-company associations during migration.

Deals in Livespace are scoped to Spaces and carry pipeline-stage data, value, owner, and timestamps. Custom deal fields vary by account. We map standard deal fields 1:1 and flag any non-standard fields for manual review before writing to the destination.

Spaces define separate working environments or pipelines within a single Livespace account. Deals belong to a Space. Where the destination CRM uses a single pipeline model, we flatten multiple Spaces into a single pipeline with a Space-label custom field to preserve context.

Tasks are assignable work items linked to Deals or Persons. The API exposes task status, due dates, owners, and body text. Completed vs open task states are preserved. Bulk creation of tasks in sequences is not exposed via public API.

Users are the licensed seats in Livespace. API exposes user records with role and team assignment. User-to-deal ownership is preserved as a User-ID reference. We do not migrate password hashes or 2FA settings — those are re-provisioned at the destination.

Teams group Users and can be assigned as deal owners. The team structure is preserved in migration, but team-to-user membership is flattened into individual user assignments at the destination if the target lacks a native team concept.

Livespace supports additional/hidden fields on Persons, Companies, and Deals. The API exposes a dedicated Get custom fields endpoint. We read the full custom-field schema before mapping, then handle type conversion (date formats, picklist values, numeric precision) per destination CRM.

Contact Groups are static segment lists. The API exposes a Get contact group list endpoint. We export group memberships as a tag or list association in the destination, noting that dynamic segments may not be migratable 1:1.

Sources track where leads originated (web form, referral, event, etc.). Livespace exposes a source list API. We map source values as a custom field on the Person record at the destination, as most CRMs do not have a native source object.

Livespace does not expose file attachments via its public REST API. Attachments on Deals and Persons must be exported separately via the application's export function or manually downloaded before migration. We flag this as a manual step in the migration runbook.

Automated email sequences are a Livespace-native feature with no public API endpoint. Sequence membership and step status cannot be programmatically migrated. We document the existing sequences so they can be rebuilt manually or via the destination's automation tooling.