Migrate from Simplero to Nutshell

Simplero Contacts map to Nutshell People records. We preserve the contact's name, email address, subscription date, and phone number directly. Simplero tags migrate as a comma-separated value in a custom text field on the Person record, or as Nutshell's native Tags if the customer has configured them pre-import. Custom Contact Fields from Simplero (e.g., interpolation key fields like phone_number, company_name, birthday) require pre-creation in Nutshell Settings before import; we document the full list of Simplero custom fields during scoping and provide a field creation checklist.

Simplero Contacts that represent pre-sale prospects or inbound leads without a closed deal map to Nutshell Lead records. We apply a source filter during scoping: contacts with no order history and no product enrollment become Leads; contacts with any purchase or enrollment become People attached to an Account. The Simplero contact creation date maps to the Lead's created date.

Simplero does not have a separate Company object; company information is stored as a custom field or tag on the Contact. We extract company name from Simplero custom fields and interpolation keys and create Nutshell Account records for each distinct company name appearing on three or more Contacts. Smaller sets of company names create as Accounts on a per-record basis. The Account serves as the parent of the Person record.

Simplero Deals (Skyrocket tier only) map to Nutshell Opportunities. The Simplero deal stage maps to a Nutshell pipeline stage; we define the stage name mapping during scoping since Simplero allows custom stage names. Deal value, close date, and owner (assigned to a scheduling user) migrate directly. Deals without an associated contact create as standalone Opportunities in Nutshell.

Simplero's single pipeline (Skyrocket) maps to a Nutshell Pipeline configured in Settings. We map Simplero stage names to Nutshell stage values and set probability percentages based on Simplero's stage settings. If the customer uses multiple pipelines in Nutshell post-migration, we document the mapping as a configuration guide for the admin.

Simplero tags are flat key-value labels applied to contacts. We export the full tag list, deduplicate, and create matching Nutshell Tags during import. Each contact's tag assignment migrates as a Tag record linked to the Person or Lead. Tags used for segmentation (dynamic groups) do not automatically rebuild as Nutshell static lists; we document the segment membership per contact for manual rebuild.

Simplero Order records (product, price, date, payment gateway, refund status) attach to the migrated Contact. We map each order as a Nutshell Task with the order details in the task description field, the purchase date as ActivityDate, and the order total as a custom currency field on the task. Refund flags and partial payments migrate as task status or a custom picklist field. Order-to-product linkage is preserved through the task's linked Person record.

Simplero Products (courses, memberships, digital downloads, coaching programs) map to Nutshell Product records if the customer uses Nutshell's product and quoting features. Pricing and access rules migrate as Product2 with Standard Price Book entries. Products without a deal association in Simplero are migrated as a reference catalog only; the customer configures the pricing integration post-migration.

Simplero Automation Flows (triggers, delays, branching conditions, and action chains) are not exposed via API or any export mechanism. We do not migrate Flow logic. During discovery we document every active Flow: trigger event, step sequence, condition branches, and action types. This becomes the rebuild guide for the customer's Nutshell admin to reconstruct in Nutshell Workflows. Complex multi-step nurture sequences require significant manual rebuild effort.

The content of individual emails within a Simplero sequence migrates as Nutshell Email Templates. We export each email step (subject, body HTML, delay before send) as a separate template with naming convention SequenceName_StepN for traceability. The sequence logic (trigger, cadence, branching conditions) does not migrate; it is documented in the Flow inventory for manual rebuild as Nutshell Workflows with time-based triggers.