Migrate from Livespace CRM to Salesforce Sales Cloud

Livespace Persons with a defined lifecycle stage of customer or evangelist map to Salesforce Contact attached to an Account. Persons with a lifecycle stage of prospect, marketing qualified lead, or unregistered visitor map to Salesforce Lead. The split rule is defined during scoping based on the customer's Livespace lifecycle configuration. We preserve the original Livespace lifecycle stage in a custom field on both Lead and Contact for audit and reporting continuity.

Livespace Company records map directly to Salesforce Account. The company domain becomes the Account Website field and is used as the dedupe key during import. Account is created before any Person import so that the AccountId Lookup relationship is satisfied at the moment of Contact or Lead insert. If the customer uses multiple Spaces with shared Companies, we deduplicate at the Account level to avoid creating duplicate Account records.

Livespace Deals map to Salesforce Opportunity. The Livespace deal stage maps to Salesforce StageName, and the Space assignment maps to a Salesforce Record Type and Sales Process that we configure before migration. Deal value, owner, expected close date, and timestamps migrate directly. Closed-Won and Closed-Lost dates and reasons from Livespace custom fields become Salesforce CloseDate and Loss Reason fields.

Livespace Spaces are independent working environments with their own deal stage pipelines. Each Space maps to a Salesforce Record Type on Opportunity, with a corresponding Sales Process that whitelists only the relevant stage values. Stage probability percentages migrate from Livespace to Salesforce StageProbability. Multi-Space accounts require the customer to decide whether to consolidate Spaces into fewer Record Types or maintain the full separation; we document the decision during scoping and implement per the agreed design.

Livespace Tasks (assignable work items linked to Deals or Persons) map to Salesforce Task records. Status, Priority, due date, owner, and body text migrate directly. Completed versus open task states are preserved. Task assignment migrates by resolving the Livespace user reference to the Salesforce OwnerId via the User mapping. Tasks linked to Deals resolve their WhatId to the migrated Opportunity ID during the Deal migration phase.

Livespace User records map to Salesforce User by email match. Role and team assignment from Livespace are noted for the customer's Salesforce admin to configure in profiles and permission sets. We do not migrate password hashes or two-factor authentication settings. Any Livespace User without a matching Salesforce User goes to a reconciliation queue for the customer's admin to provision before record import resumes.

Livespace Teams group Users and can be assigned as deal owners. If the destination Salesforce org uses the native Salesforce Group object for team grouping, we map Teams to Groups and team memberships to GroupMember records. Where the customer's workflow relies on team-level deal ownership rather than individual ownership, we create a custom Team__c object with a lookup to User to preserve the team assignment semantics beyond the native Group model.

Livespace additional and custom fields on Persons, Companies, and Deals are read via the Get custom fields endpoint before any data migration begins. We create equivalent Salesforce custom fields with matching API names and data types. Picklist values map directly; date fields are normalised to the Salesforce date format; multi-select picklists in Livespace map to Salesforce multi-select picklists. Any Livespace custom field with no Salesforce equivalent is created as a Text field with a migration note in the field mapping document.

Livespace Contact Groups are static segment lists. We export group memberships during the Person export phase and create Salesforce Campaign records with CampaignMember records linking each migrated Lead or Contact to the appropriate Campaign. Dynamic Contact Groups that use filtering rules rather than static membership cannot be recreated programmatically; we document the filter criteria in the migration deliverable so the customer can build an equivalent Salesforce report or dynamic list post-migration.

Livespace Sources track where leads originated (web form, referral, event, cold outreach). We map source values to a custom Lead Source field on the Contact and a custom text field on the Lead. If Salesforce Professional or above is in use, we use the standard Lead Source picklist and normalise Livespace source values to the nearest Salesforce picklist entry, flagging any values that require a custom picklist entry.

Livespace Tickets migrate to Salesforce Case if the destination Salesforce org includes Service Cloud. Livespace ticket pipeline stages map to Case Record Types, and ticket status values map to Case Status picklist entries. Ticket conversation history migrates as EmailMessage records linked to the Case. If the destination org does not include Service Cloud, Tickets are mapped to custom Opportunity Task records or a custom Ticket__c object, with the customer's preference recorded during scoping.

Livespace email engagement records (visible through the API as activities linked to Persons or Deals) migrate to Salesforce EmailMessage records with the email body and metadata, linked to an Activity Task record for the timeline entry. WhoId on the Task points to the migrated Lead or Contact; WhatId points to the related Opportunity or Account. Email direction (sent vs received) is preserved in a custom EmailDirection field.

Livespace call engagements map to Salesforce Task with TaskSubtype = Call. Call disposition, duration, and any recording URL preserved in custom Task fields. Activity ordering is maintained by setting ActivityDate to the original Livespace timestamp. Call assignments migrate by resolving the Livespace owner reference to the Salesforce OwnerId.

Livespace note engagements migrate to Salesforce Note records linked via ContentDocumentLink to the parent Person, Company, or Deal record at the destination. Rich text formatting in Livespace notes is preserved as Salesforce Note rich text. If the customer uses Salesforce Lightning Experience, Notes are migrated to ContentNote records to align with the modern content storage model.