Migrate from Factoreal to Nutshell

Factoreal Contacts map to Nutshell People records. Standard fields (name, email, phone, address) transfer directly via CSV preprocessing. Custom fields defined on Factoreal contacts are identified during discovery, their values extracted per record, and mapped to Nutshell custom fields created in the destination account before import. The Factoreal contact ID is preserved in a custom field for cross-system reference during the reconciliation window.

Factoreal Company records map to Nutshell Accounts. Company name becomes Account name, and the domain or website URL maps to the Account's website field. If Factoreal contacts carry a company association, we resolve the Account reference before inserting People records so that the relationship is satisfied at import time rather than patched afterward.

Factoreal Segments define filter rules on contact attributes and behavioral events. We reconstruct segment membership as Nutshell Tags, with each Factoreal segment name becoming a tag label. During migration, contacts that were members of a given segment receive the corresponding tag in Nutshell, preserving the group affiliation without migrating the filter logic itself. The filter definitions are documented separately for the customer's admin to potentially recreate as Nutshell saved filters.

Factoreal Campaigns hold subject lines, content, send history, and engagement metrics across email, SMS, and WhatsApp channels. We map campaign structure to Nutshell Activity records with a custom activity type (e.g., Campaign Email, Campaign SMS) to distinguish them from standard sales activities. Open rates, click rates, and send timestamps migrate as metadata on the activity record. Note that Nutshell's Activity model differs from Factoreal's Campaign model in structure; we preserve the campaign name, date, and performance summary as a referenceable activity log rather than a native campaign object.

Factoreal automation workflows define trigger conditions and multi-step action sequences across channels. These workflows are not stored in an exportable, portable format. We capture the workflow graph — triggers, conditions, delays, and action steps — as documentation in a written automation inventory. Nutshell's automation capabilities (task assignments, pipeline automation, email templates) require a separate rebuild in Nutshell by the customer's admin team.

Factoreal email templates include HTML content and dynamic merge field placeholders. We extract the template HTML from each exported template and deliver it as a file package. Merge field syntax is documented per template with the Nutshell equivalent format noted. Visual rendering differences between Factoreal's template editor and Nutshell's email content editor mean that templates require a visual review and rebuild in Nutshell rather than a direct import.

Factoreal custom fields on contact and company records are identified during discovery and exported with their per-record values. We create matching custom fields in Nutshell on the corresponding object (Person or Account) using Nutshell's custom field configuration, matching the field type (text, number, date, dropdown) to the closest Nutshell equivalent. Multi-select or tag-style custom fields map to Nutshell tags with a flag noting the original field name.

Factoreal contacts can carry multiple tags defining behavioral attributes, source data, or segmentation labels. We export the full tag list per contact and create equivalent tags in Nutshell, applying the tag-to-person association during the Person import phase. The many-to-many relationship between contacts and tags is preserved in the target system.

Channel-level message logs from Factoreal's SMS and WhatsApp campaigns are included in the contact and campaign export files. We extract send timestamps, direction (inbound or outbound), and message content, mapping them to Nutshell Activity records with a custom activity type (SMS or WhatsApp). The activity is linked to the corresponding Person record in Nutshell.

Factoreal's built-in e-commerce integration captures order records, line items, and product SKUs. Order and product data are not native Nutshell CRM objects. We export the full order and product dataset from Factoreal as a structured CSV package and deliver it separately. If Nutshell includes the e-commerce integration add-on or if the customer uses a connected tool like WooCommerce or Shopify alongside Nutshell, the order records can be imported through that connector. We document the order data schema and field mapping recommendations for the customer's admin to implement in their preferred order management workflow.