Migrate from Livespace CRM to Zoho CRM

Livespace Persons with lifecycle stage values migrate to Zoho Lead or Contact based on a split rule defined during scoping. Persons with a qualified buyer stage map to Zoho Contact linked to an Account; all others map to Zoho Lead. The original Livespace lifecycle stage is preserved in a custom field on both Zoho Lead and Contact for reporting continuity. Email, phone, address, and all standard Person fields migrate 1:1.

Livespace Companies map directly to Zoho Accounts. Company domain stored in Livespace's website field becomes the Account Website field and serves as the dedupe key during import. Person-to-Company associations are preserved as the AccountId lookup on Contact records at migration time. Multi-branch companies in Livespace map to multiple Zoho Account records if the customer confirms the flat structure during scoping.

Livespace Deals map to Zoho Deals with StageName derived from the Livespace pipeline stage. Deal value, owner, expected close date, and all custom deal fields migrate 1:1. Custom field values are written after Zoho schema creation in the discovery phase, so field IDs are resolved before Deals are inserted. Closed-Won and Closed-Lost reason fields map to Zoho custom Loss Reason and Won Reason picklist fields.

Livespace Spaces define separate working environments or deal pipelines. Each Livespace Space maps to a Zoho CRM Pipeline (created via Blueprint in Zoho). The Space's stage values map to Zoho pipeline stages in sequence order. If the customer has more than 5 Zoho pipelines, we flag the pipeline count during scoping because Zoho's pipeline UI complexity increases with count. Spaces with no Deals are skipped but documented.

Livespace Tasks linked to Deals or Persons migrate to Zoho Tasks with Subject, Status, Due Date, and body preserved. Completed vs open task states map to Zoho Task Status (Not Started, In Progress, Completed). Owner resolution uses the User mapping built from email match. Tasks without a valid owner match are placed in a reconciliation queue for the customer's admin to resolve before migration resumes.

Livespace Users map to Zoho Users resolved by email address. Role and team membership in Livespace map to Zoho profile and timezone settings. We do not migrate password hashes or 2FA configuration. Any Livespace User not found in the Zoho destination org by email is flagged in the reconciliation report for the customer's admin to provision before production migration.

Livespace Teams group Users and can be assigned as deal owners. Team membership is flattened into individual User assignments in Zoho because Zoho's permission model uses profiles and roles rather than a separate Team entity. We document the original Livespace team structure in the migration handoff so the customer's admin can rebuild team-based reporting in Zoho.

Livespace additional/hidden fields on Persons, Companies, and Deals are discovered via the Get custom fields endpoint before any Zoho schema is created. We create Zoho custom fields with matching data types and character limits (validated against Zoho field type documentation) before writing any record. Date formats from Livespace are normalised to ISO 8601 with explicit UTC offset for Zoho. Picklist values are enumerated and mapped to Zoho picklist options.

Livespace Contact Groups (static segment lists) are exported as tag assignments on the corresponding Zoho Contact or Lead records. If the customer uses Zoho Campaigns, groups can alternatively map to Campaign membership. Dynamic segments in Livespace (which evaluate in real time) cannot be reproduced identically in Zoho and are documented as a manual segmentation rebuild item.

Livespace Sources (web form, referral, event, etc.) are tracked at the Deal level via the Sources API. We map source values to a Zoho custom field on the Deal module. If the customer also captures source at the Person level, we create a second custom field on Contacts and Leads. The source value list is enumerated during discovery and whitelisted as a Zoho picklist field.

Livespace does not expose file attachments via its public REST API. Any files attached to Deals or Persons must be downloaded manually via the application's export function before migration or exported via Livespace's bulk export tool. We flag this as a pre-migration manual step in the runbook, exclude attachment records from the API-driven migration scope, and deliver a checklist of all attachment-bearing records so no file goes unmapped.

Livespace email sequences have no public API endpoint. Sequence membership, step status, and timing rules cannot be read programmatically. We document the existing sequences in a written summary delivered at migration close, with recommended Zoho Workflow or Blueprint equivalents for each sequence step. The customer's admin rebuilds sequences in Zoho using the documentation as a specification. This is not data loss but a source-platform API limitation.