Migrate from Spark CRM to Zoho CRM

Spark CRM contacts map directly to Zoho CRM Leads when the source record represents an unqualified or unconverted prospect. The Last Name field is mandatory in Zoho Leads — Spark contacts without a last name default to a placeholder that FlitStack flags for manual review before import commits.

Spark CRM contacts that have been marked as customers or that have a linked closed deal map to Zoho CRM Contacts. Contacts in Zoho require an Account lookup — Spark contacts without a company association land on a default placeholder Account that FlitStack surfaces for resolution after migration.

Spark CRM companies map 1:1 to Zoho CRM Accounts using the Account_Name field. Parent-child company hierarchies in Spark CRM are preserved via Zoho CRM's Parent Account lookup. Multi-company associations per contact are handled by creating one primary Account link and surfacing secondary links as Account Contact Relation records.

Spark CRM deals map to Zoho CRM Deals. The Deal_Name maps to Deal_Name, amount to Amount, and close date to Close_Date. Zoho Deals do not have a native probability field at the standard-object level — if Spark stores probability on the deal, FlitStack creates a custom field to preserve the value.

Spark CRM pipeline stages map to Zoho CRM deal stage picklist values by name. Stage order and probability are read from Spark and re-applied in Zoho's stage configuration. If Spark and Zoho share a stage name (e.g., Closed Won), the mapping is direct; otherwise each unmatched stage is flagged for Zoho admin to pre-create the picklist value before the bulk import runs.

Spark CRM custom properties that have no Zoho CRM native equivalent are created as custom fields in the target module before migration. FlitStack reads the custom property metadata from Spark's API, creates the field in Zoho via the Settings Fields API, and then populates it during the bulk import. Multi-select custom properties require their picklist values to be pre-registered in Zoho.

Spark CRM email records migrate as Zoho CRM Tasks with the Type field set to Email. Subject, body content, timestamp, and owner are preserved. If Spark stores email as an HTML body, FlitStack strips scripts and inline styles before inserting into Zoho's plain-text Task.Body field.

Spark CRM call logs migrate as Zoho CRM Tasks with Type set to Call. Duration, call outcome, and any notes recorded in Spark are stored in Zoho's Task.Subject and Task.Description fields. Call recordings, if stored as file attachments in Spark, are re-uploaded to Zoho Files and linked to the corresponding Task.

Spark CRM meetings map to Zoho CRM Events with start time, end time, location, and attendees preserved. Recurring meetings are migrated as a single Event in Zoho — FlitStack notes the recurrence pattern in Event.Description for manual recreation in Zoho's calendar module if needed.

Spark CRM notes migrate as Zoho CRM Notes with parent record lookup preserved. Rich-text formatting is retained where Spark's export format allows; plain-text fallbacks are used for non-HTML note bodies. Notes attached to multiple records in Spark are migrated as separate Note records in Zoho linked to each parent.

File attachments in Spark CRM are downloaded to temporary storage and re-uploaded to Zoho CRM's Attachments module using the Attachments API. Each file is linked back to its parent record (Contact, Account, or Deal) via the Related_Details lookup. Zoho's 25MB per-file limit is enforced — files exceeding this threshold are flagged for manual chunking before re-upload.

Spark CRM owner IDs are resolved to Zoho CRM users by email match. Before migration, FlitStack fetches the full user list from Zoho CRM via GET /crm/v8/users and builds an email-to-user-ID lookup table. Unmatched owner IDs are logged and records are assigned to a fallback user pending Zoho admin action.