Migrate from Spark CRM to Nutshell

Spark CRM People map directly to Nutshell People. Standard fields (name, email, phone, address) migrate as direct mappings. The primary Company association becomes the Nutshell Person's Company link. Owner resolution happens via email match to Nutshell users before records commit.

Spark CRM Companies map directly to Nutshell Companies. Company name, domain/website, industry, employee count, and annual revenue transfer as direct or value‑mapped fields. Parent‑company hierarchies in Spark become Parent Company links in Nutshell where supported. The mapping also includes phone number, address, and any custom fields on the Company object. We resolve any duplicate company names by appending a numeric suffix.

Spark CRM Leads map to Nutshell Leads without transformation. Lead status, source, and any custom fields migrate to Nutshell Lead custom fields. Unconverted Spark Leads (status 'open') land as active Nutshell Leads ready for follow‑up assignment. We also preserve the original lead creation date and owner email for audit trail purposes.

Spark CRM Deals map to Nutshell Deals with stage name value-mapping. Deal name, amount, close date, and owner transfer directly. Pipeline association in Spark maps to Nutshell's single-pipeline model; if Spark uses multiple pipelines, each becomes a separate Deal category or tag in Nutshell.

Spark CRM activity records (calls logged, emails tracked, meetings scheduled) become Nutshell Activities attached to the corresponding Person, Company, or Deal. Activity type, subject, date/time, duration, and outcome notes transfer. Owner preserves as the activity creator. If an activity references a contact that hasn't been migrated yet, we queue it for later attachment after the contact is created.

Spark CRM Notes attached to People, Companies, or Deals migrate as Nutshell Activities with type 'Note'. Rich‑text formatting in Spark Notes is preserved as plain text or HTML in Nutshell Activity notes, depending on the source format. Any embedded images or file links are converted to attachment references or stored as URLs for convenient access.

Spark CRM custom fields on People require pre-creation of matching Nutshell Person custom fields before migration. Field types (text, number, date, picklist) are preserved. Picklist values are mapped value-by-value; any values without Nutshell counterparts are flagged for admin review before the full run.

Spark CRM company custom fields (e.g., industry‑specific identifiers, account numbers) migrate to Nutshell Company custom fields. Nutshell's per‑object custom field limits apply; most SMB plans accommodate 20+ custom fields per object type. We also map any pick‑list values to Nutshell's pick‑list options, flagging mismatches for manual review.

Spark CRM Deal custom fields (e.g., deal type, product line, renewal date) map to Nutshell Deal custom fields. These fields are available for reporting and filtering in Nutshell's Deal view after migration completes. If a custom field uses a dependent pick‑list, we preserve the dependency structure to the extent Nutshell supports it.

Spark CRM file attachments on People, Companies, or Deals are re‑uploaded to Nutshell as file attachments on the corresponding record. File size limits apply per Nutshell's attachment constraints. We verify file integrity (MD5 checksum) before and after upload. We also retain the original file name and creation timestamp to preserve context.

Spark CRM owner assignments on records resolve to Nutshell users via email address match. Unmatched owners are flagged before migration; your team either creates Nutshell user accounts for them or assigns records to a fallback owner before the full run commits.

Spark CRM workflows, sequences, and automation rules do not migrate. They are exported as a structured JSON document describing triggers, conditions, and actions so your Nutshell admin can rebuild equivalent logic using Nutshell's workflow builder or third‑party automation tools. The JSON includes field names, operator types, and expected values for each step, facilitating accurate reconstruction.