Migrate from Livespace CRM to Pipedrive

Livespace Persons map directly to Pipedrive People. Standard fields (name, email, phone, address) migrate 1:1. The person's lifecycle_stage, source attribution, and any custom fields from the Get custom fields endpoint map to corresponding Pipedrive People custom fields. We resolve the Person-to-Company link and write the OrganizationId reference after Organizations are created.

Livespace Companies map to Pipedrive Organizations. Company name becomes Organization name, domain fields map to website, and industry classification maps to a Pipedrive custom field if the destination has industry values configured. Organization is created before any Person import so that the org_id reference is satisfied at the moment of Person insert.

Livespace Deals map to Pipedrive Deals with the Space's pipeline stage mapping to the corresponding Pipedrive Stage within the target Pipeline. Deal value (numeric), currency, owner, expected_close_date, and stage_timestamps migrate directly. Custom deal fields from Livespace map to Pipedrive Deal custom fields. The deal-to-Space assignment determines which Pipedrive Pipeline receives the Deal.

Livespace Spaces define separate working environments or sales processes. Pipedrive uses Pipelines with Stages. If the Livespace account has one Space, it maps to one Pipedrive Pipeline with its configured Stages. If multiple Spaces exist, each Space maps to a separate Pipedrive Pipeline. Stage names and probabilities from the Livespace Space configuration are translated into Pipedrive Stage definitions during destination setup. Teams using Spaces to separate business units (e.g., Enterprise vs SMB) must decide whether to create separate Pipelines or consolidate into one — this decision is made during scoping.

Livespace Tasks assignable to Deals or Persons map to Pipedrive Activities (type Task). Task subject, body text, status (open/closed), due date, and owner migrate. Completed vs open state is preserved as the Activity's completed flag. The task-to-deal link migrates as the Pipedrive Deal reference on the Activity record.

Livespace Users (licensed seats) map to Pipedrive Users resolved by email address match. Role and team assignment from Livespace maps to Pipedrive admin vs regular user role. We do not migrate password hashes or 2FA settings. Any Livespace User without a matching Pipedrive User (created during destination setup before migration begins) is placed in a reconciliation queue.

Livespace Teams group Users and can own Deals. Pipedrive Teams serve the same grouping function. Team membership is preserved as team-to-user assignments. Pipedrive Teams cannot be assigned as Deal owners directly — team-scoped deals must be reassigned to the team lead User record. Teams used purely for permissions in Livespace may need a role review in Pipedrive.

Livespace additional/hidden fields on Persons, Companies, and Deals are discovered via the Get custom fields endpoint at migration start. Each custom field's type (text, number, date, picklist, checkbox) maps to the corresponding Pipedrive custom field type. Picklist values are enumerated explicitly in the Pipedrive destination before migration so that the import does not reject values outside the allowed set. Date formats are normalised to ISO 8601 (YYYY-MM-DD) to match Pipedrive's expected format.

Livespace Contact Groups (static segment lists) export from the Get contact group list endpoint. We create corresponding People Groups in Pipedrive and assign each Person to the relevant group memberships. Dynamic segments (if configured in Livespace) are noted as non-migratable and can be rebuilt as Pipedrive Filter views.

Livespace Source values (web form, referral, event, etc.) are exported from the source list API and mapped as a custom field on the Pipedrive People record. Pipedrive does not have a native 'source' concept, so a single-select or text custom field carries the attribution data for reporting segmentation.

Livespace does not expose file attachments via its public REST API. Attachments on Deals and Persons must be downloaded manually via the application UI before migration begins. We flag this as a mandatory pre-migration step in the runbook and exclude attachment records from the API-driven migration scope. Pipedrive accepts attachments via the Activity file upload API post-migration, but the source files must be in the customer's possession before cutover.

Livespace's email sequence builder exposes no public API endpoints. Sequence membership, step status, timing rules, and enrollment conditions cannot be read or migrated programmatically. We document the existing sequences (enrolled contacts, step count, delay between steps, and action types) in a written summary so the customer's admin can recreate them in Pipedrive's Campaigns automation feature (available on Advanced plan and above). This is not data loss — it is a source platform API limitation requiring manual rebuild.