Migrate from SimplyConvert to Nutshell

SimplyConvert's case-centric model has no direct Nutshell equivalent — matters must be decomposed into Deals

SimplyConvert treats a legal case as the top-level record; everything (client, documents, conversations, referrals) links to the Case. Nutshell has no Case object — only People, Companies, Leads, and Deals. When migrating, the Case ID becomes the Deal name, settlement value becomes the Deal amount, and all linked conversation history becomes Tasks attached to that Deal. Any practice-area logic that SimplyConvert encodes in separate intake forms must be rebuilt as custom fields or pipeline-stage rules in Nutshell. If your firm runs multiple practice areas as entirely separate workflows in SimplyConvert, plan for 2–4 hours of Nutshell admin configuration per practice area post-migration to restore that segmentation.

Referral routing logic in SimplyConvert has no Nutshell equivalent and must be rebuilt manually

SimplyConvert's Referral Platform captures the referring partner, routing decision (accept, reject, refer onward), and any referral fee arrangements — all as structured data linked to the Case. Nutshell has no referral object, no routing workflow, and no native referral-fee field. We preserve referral attribution as custom fields on the Deal (Referral_Source__c, Referred_Out__c, Referral_Partner__c), but the routing logic — auto-routing to the right attorney, auto-rejecting based on conflict checks, sending referral notifications — must be rebuilt in Nutshell's automation tools (sequences, task rules). Budget 1–2 days for a Nutshell admin to configure the referral routing workflow after data lands.

Intake qualification scores and AI auto-rejection decisions do not migrate as native Nutshell fields

SimplyConvert's AI chatbot outputs a qualification score (0–100) and a binary decision (Qualified / Rejected / Referred) based on the firm's criteria tree. Nutshell has no native qualification scoring and no auto-rejection logic. We migrate the score and decision as custom fields on the Person record (Intake_Score__c, Intake_Qualification__c), but the firm's criteria tree — the branching logic that evaluates case type, damages, jurisdiction, and statute of limitations — cannot be imported. It must be rebuilt as Nutshell automation rules or a separate qualification tool. If the criteria tree is complex (20+ branching rules), allocate 3–5 days for a legal operations review and Nutshell configuration.

Nutshell's single-pipeline view requires custom fields to segment by practice area

SimplyConvert maintains separate intake configurations per practice area (mass torts, employment, medical malpractice). Each practice area has its own chatbot form, qualification criteria, and case workflow. Nutshell has a single Deal pipeline — you cannot create separate pipelines for separate practice areas without purchasing multiple Nutshell workspaces (which requires separate Nutshell accounts). To preserve practice-area segmentation in Nutshell, we create a Practice_Area__c custom picklist field on Deal and configure Nutshell's List view filters accordingly. This is a functional limitation: Nutshell cannot enforce different stage progressions per practice area within one account without custom development.

Nutshell API rate limits on find operations may extend migration timelines for large case volumes

Nutshell's API rate-limits find operations (e.g., findPeople, findLeads) with non-stub responses, while add and edit operations carry no explicit cap. SimplyConvert's case export can return all records in one API call, but Nutshell's read-side limits mean we must paginate large result sets in batches. For migrations exceeding 10,000 records, expect a 15–25% timeline extension due to Nutshell's read-side throttling. We mitigate this by using Nutshell's bulk export endpoint where available and interleaving read and write operations to stay within fair-use bounds.