Migrate from Leadfwd to Nutshell

Leadfwd Contacts map directly to Nutshell Contacts. The Salesforce Contact ID is preserved as a custom field sf_contact_id__c for audit and any future Salesforce re-sync. Standard Contact fields (name, email, phone, title, address) migrate directly. Any custom fields on Leadfwd Contacts require manual mapping to Nutshell custom fields or notes fields because Nutshell does not expose a field-level API mapping interface equivalent to Salesforce Field API.

Leadfwd's Lead records (if present, since Leadfwd treats Leads and Contacts interchangeably as enrollment targets) merge into Nutshell Contacts. The original Lead_Status is preserved as a custom text field original_lead_status__c. Because Nutshell does not have a separate Lead object, any scoring data or status values that exist in Leadfwd carry over as contact-level custom fields.

Leadfwd Company records map directly to Nutshell Company. The Company ID is preserved as sf_account_id__c for audit. Any custom Company properties (industry classification, employee count, revenue) map to Nutshell's standard Company fields or custom fields if the customer has configured them. Industry data accuracy issues noted in Leadfwd reviews are flagged for QA review before migration finalization.

Active sequence enrollments cannot resume in Nutshell because Nutshell has no sequence engine. We export enrollment records (Contact name, Sequence name, current step, enrollment date, last activity date, status) as Nutshell Activity records of type Note. The Note body contains structured text: sequence name, step index, status, and timestamps. The customer's admin uses this as the reference list for manually re-enrolling contacts in Nutshell's workflow automation or a parallel sales engagement tool.

Icebreakers are Leadfwd-specific AI-generated conversation openers using LinkedIn profile data. These cannot activate in Nutshell. We export the generated text and the LinkedIn profile URL as a Nutshell Activity Note on the relevant Contact. The customer's sales team can reference the original opener and manually incorporate it into outreach. The AI-generated variants are non-portable and require re-generation if the customer uses a similar AI tool in Nutshell.

Leadfwd email engagement events migrate to Nutshell Activities of type Email. The activity body carries the email subject and a timestamp. Open, click, reply, and bounce status flags are stored as custom fields on the Activity (email_opened__c, email_clicked__c, email_replied__c, email_bounced__c) so that the engagement history is visible on the Contact timeline in Nutshell without requiring a separate engagement scoring add-on.

Leadfwd call events migrate to Nutshell Activities of type Call. Call duration (in seconds) and disposition notes from Leadfwd map to Nutshell call duration and result fields on the Activity record. The Activity is linked to the Contact. Call recording URLs from Leadfwd cannot be exported and are noted as requiring re-upload or re-linking to the Nutshell Activity manually.

Leadfwd LinkedIn connection and meeting events migrate to Nutshell Activities of type Meeting. The activity name carries the event type (LinkedIn Connection, LinkedIn Message, Meeting) and the timestamp. LinkedIn message content cannot be migrated due to platform API restrictions, but the event occurrence and Contact association are preserved. Meeting events with calendar data (if available) map to Nutshell meeting details.

Leadfwd Tasks map to Nutshell Tasks with Status, Priority, Due Date, and Assignee preserved. Task assignment resolves by matching Leadfwd owner email to Nutshell user email. Any automated task logic (auto-created from Sequence steps) does not transfer and is recreated as standard Nutshell Tasks by the admin post-migration.

Leadfwd custom fields on Contact and Company sync through the Salesforce API pipeline. We map them field-by-field to Nutshell custom fields. Nutshell supports custom fields on Contacts and Companies via its API. Any custom field referencing Leadfwd-specific picklist values (e.g., Sequence enrollment status) is migrated as a text field rather than a picklist because the value set is Leadfwd-specific and not reusable in Nutshell. We audit the full custom field list during scoping and flag any field with a Leadfwd-specific dependency.