Migrate from Leadfox to Nutshell

Leadfox Contacts map directly to Nutshell People. Standard fields (name, email, phone, address) migrate to the corresponding Nutshell People fields. We resolve the owner assignment by matching Leadfox owner email against Nutshell User email at migration time. Custom fields attached to Contact records map to Nutshell custom fields, preserving field type (text, number, date, dropdown) and multi-select behavior. Contact records are imported first to establish the primary Person records before any related object imports begin.

Leadfox supports unlimited custom fields per Contact. We export the full field definition schema (field name, API-style label, data type, and picklist values) alongside the data. Each custom field is pre-created in Nutshell with the equivalent type before Person import begins. Dropdown fields become Nutshell picklists; multi-select becomes Nutshell multi-select; text, number, and date fields map directly. Field-level dependencies and conditional visibility are not exported and must be reconstructed manually in Nutshell Settings.

Leadfox Tags are applied at the Contact level as single or multi-value labels. We export all tag assignments as a flat list per Contact and map them to Nutshell's tag system on Person records. If the customer uses a large tag vocabulary (over 100 distinct tags), we discuss whether to use Nutshell multi-select picklist fields or the tag feature during scoping. Tags used for segmentation logic that depended on dynamic behavior become a written list for manual re-segmentation in Nutshell.

Leadfox Segments are dynamic lists based on filter criteria (field values, score thresholds, tag combinations). We export the current membership of each Segment as a static Contact list. The dynamic filter definition is documented as a written step: for each Segment, we list the filter conditions and the count of members at export time. Nutshell's Saved Filters replicate the access-to-filtered-view behavior, but the dynamic refresh logic is not exported.

Leadfox calculates numeric lead scores based on behavioral rules (page visits, email opens, form submissions, custom triggers). We export the current score value as a static integer on each Contact record and map it to a Nutshell custom number field score__c. The underlying scoring rules (point values per action, threshold triggers, grade tiers) are not exported. We deliver a written scoring rule map so the customer's admin can rebuild the scoring logic in Nutshell using nutshell automation rules or a scoring add-on.

Leadfox enforces CAN-SPAM compliance by tracking unsubscribe status per Contact. We export the current opt-out flag and suppression list entries and apply them to Nutshell People as the email subscription status field. Any Contact with a Leadfox unsubscribe flag is set to the equivalent opt-out state in Nutshell before the first email campaign is launched from the new platform.

Leadfox Email Templates are stored with dynamic personalization tokens in the Content Studio. We export template HTML and the token-to-field mapping as a structured reference document. Nutshell does not host a template content library equivalent to Leadfox's Content Studio; the customer rebuilds templates using their chosen email sending tool (Nutshell's built-in email or an external platform). We preserve the token map so personalization fields can be reconnected without reverse-engineering the original template logic.

Leadfox landing pages are built with the platform's drag-and-drop page builder and are not exportable as editable assets. We export page content as an HTML snapshot and the field-to-field mapping for each form embedded on the page. The highest-converting pages by submission volume are flagged in the reference document so the customer can prioritize rebuilding those in Nutshell Forms, Web-to-Lead, or an external landing page tool first.

Leadfox automation sequences (triggers, time delays, conditional branches, goal steps, A/B test splits) are stored in a proprietary format. We document every active workflow as a step-by-step action map with trigger conditions, action types, delay values, and branch logic. Nutshell's workflow capabilities are more limited (basic automation rules, nutshell Campaigns for email cadences), so the map includes a best-effort Nutshell equivalent for each step. Complex multi-branch workflows with goal tracking and A/B variants require manual reconstruction and are explicitly out of scope for data migration.

Leadfox stores campaign names, UTM parameters, keyword performance, and search tracking data per campaign. We export this as a structured reference table listing campaign name, tracking source, UTM values, and the contact count reached. The actual analytics (open rates, click rates, conversion attribution) are not exported as these live in Leadfox's reporting layer, not in the contact record. The reference table is used by the customer's marketing team to reconfigure tracking in their new analytics stack.