Migrate from Devi to Nutshell

If Devi exports a contact record structure (name, email, phone, social handle), it maps to Nutshell Contact. We use the Nutshell JSON-RPC API's editContact method with the rev field for cache-safe updates. The contact's email address serves as the dedupe key. Custom fields from Devi's export map to Nutshell's customFields dictionary if the customer has configured them in Nutshell. If Devi has no contact export, we coordinate with Devi support for a manual data pull and normalize the output to Contact fields before API ingestion.

If Devi's export includes company or organization data tied to contact records, it maps to Nutshell Account. The Account is created first so that AccountId is available as a Lookup when Contact records are ingested. Nutshell's findAccounts method allows post-import reconciliation against the source export. If Devi has no company-level object (as implied by its narrow social-selling focus), contacts are migrated without Account linkage and the customer's admin decides whether to create Accounts from the company domain on email addresses post-migration.

Devi's core feature is high-intent lead detection on social media, which implies a lead record with intent signals and source attribution. We map this to Nutshell Lead, preserving intent score or signal metadata in a custom field (e.g., intent_signal__c) or the Lead Description field. The lead's social media source (LinkedIn, Twitter/X, etc.) maps to a custom field or the Lead Source picklist if the source platform is among Nutshell's allowed values.

If Devi's export includes deal or pipeline stage data (e.g., stages named after social media intent levels or custom workflow stages), we map them to Nutshell Opportunity with a Nutshell Sales Process configured to match the source stage names. If Devi has no deal or pipeline object, this step is omitted and the customer builds Opportunity workflows in Nutshell post-migration. We document any inferred pipeline stages in the migration inventory so the admin can configure them in Nutshell.

Devi generates visual content with AI as a core feature. Nutshell does not have a native media asset or content library object, but AI-generated images or copy can be stored as Note records with file attachments via ContentDocument and ContentDocumentLink. We flag this as a content migration gap: if the customer needs to preserve AI-generated content as linked attachments, they must provide the files separately and we attach them to the relevant Contact or Lead record. No automated media migration path exists.

If Devi's export includes user or team member records (name, email, role), we resolve them by email against Nutshell Users in the destination org. Any Devi's user without a matching Nutshell User is placed in a reconciliation queue for the customer's admin to provision. Nutshell supports roles and permissions per user, which we document in the handoff inventory for admin configuration post-migration.

Nutshell supports custom fields on Leads, Accounts, and Contacts via the customFields dictionary in its JSON-RPC API. We pre-create any custom fields in Nutshell before ingesting data, using the field names and types from Devi's export. The Stack Overflow documentation for Nutshell API confirms that custom field values are passed as key-value pairs inside the customFields object and null can be used to delete a value. We coordinate custom field creation with the customer during the discovery phase.

Devi's social media lead detection implies interaction history: which posts triggered a lead, which profiles were marked high-intent, and engagement timestamps. Nutshell has no social listening or social media interaction object. We map this data to Note records attached to the relevant Lead or Contact, with the Note body containing the interaction summary (profile, trigger, timestamp). The customer should confirm whether this interaction data is included in any Devi export before migration begins.