Migrate from The Service Manager to Nutshell

The Service Manager's contact or customer record maps directly to Nutshell's Person object. Person fields — name, email, phone, title, address — carry over with direct field mapping. If The Service Manager stores multiple roles per person, the primary role maps and secondary roles are preserved as a note or tag.

The organization or company record in The Service Manager maps to Nutshell's Account object. Account-level fields — company name, domain, industry, employee count, revenue — migrate directly. Nutshell Accounts can have multiple associated People; The Service Manager's company-contact links are recreated as Nutshell Person-Account associations.

If The Service Manager distinguishes between active customers and unqualified prospects, the prospect record maps to Nutshell's Lead object. Lead status, source, and owner fields carry over. Leads that convert to customers during the migration window are re-routed to Person or Account as appropriate.

The deal or opportunity record in The Service Manager maps to Nutshell's Deal object. Deal name, amount, stage, and expected close date carry directly. Nutshell's Deal object is associated with one primary Account and can reference multiple Persons (the deal team). The Service Manager's deal-owner link resolves via email match against Nutshell users.

If The Service Manager uses a pipeline model with ordered stages, each pipeline becomes a Nutshell Pipeline. Stage names are mapped value-by-value into Nutshell's stage pick-list for that pipeline. Probability and forecast-category values are set in Nutshell's stage configuration post-migration based on the source stage weights.

Logged calls, emails, and meetings in The Service Manager map to Nutshell Activities — Call, Email, and Meeting types respectively. Original timestamps, activity subject/body, and owner (resolved by email) are preserved. Nutshell's Activity timeline on a Person or Deal record displays the full engagement history.

Notes in The Service Manager migrate as Nutshell Notes attached to the corresponding Person, Account, or Deal record. File attachments are downloaded from the source and re-uploaded to Nutshell's file storage, linked to the target record. If the source API excludes attachments, FlitStack AI flags the gap and provides a separate file inventory for manual re-upload.

Custom fields in The Service Manager require Nutshell-side field creation before data can land. FlitStack AI creates the equivalent custom field in Nutshell under the appropriate object tab (Company, Person, or Lead), matching the field type — text, number, date, pick-list, or checkbox. Field options are mapped value-by-value for pick-list fields.

Owner or assigned-user records in The Service Manager resolve to Nutshell Users by email address. FlitStack AI builds a cross-reference table of source owner email → Nutshell user ID before migrating any record that has an owner assignment. Unmatched owners are flagged and assigned to a fallback Nutshell user or a dedicated 'Unassigned' placeholder.

Workflows, automation rules, SLA triggers, and notification templates in The Service Manager have no direct equivalent in Nutshell's object model. These are not migrated. FlitStack AI exports a machine-readable definition of each workflow (trigger conditions, action steps, recipients) so your Nutshell admin can rebuild equivalent logic in Nutshell Automation or sequence rules.

Saved reports and dashboard configurations in The Service Manager do not migrate because they reference source-specific field IDs and schema. The underlying data (contacts, deals, activities) migrates fully, so Nutshell's reporting tools can reconstruct equivalent views. FlitStack AI delivers a data inventory documenting what moved and where each field landed in Nutshell's object model.