Migrate from Sercom to Nutshell

Sercom person records map directly to Nutshell People. The primary company association becomes the Company lookup field on the Person record. Multi-company assignments in Sercom are preserved by establishing the primary association and documenting secondary links in a custom migration note field for admin reference after migration completion.

Sercom accounts translate to Nutshell Companies. Company name, domain, industry, and address fields map directly to their Nutshell equivalents. Parent-account hierarchies in Sercom are translated to Parent Company links in Nutshell where the destination object model supports this hierarchical relationship.

Sercom leads route to Nutshell Leads when the source record status indicates an unqualified prospect. Status, source, and rating fields map to Nutshell's Lead object fields. Unconverted leads retain their original create timestamp for reactivation workflows post-migration.

Sercom deals or service orders become Nutshell Deals. The deal name, amount, close date, and stage map to the corresponding Nutshell Deal fields. Stage values require value-by-value mapping when Sercom uses non-standard stage labels — we surface this in the migration plan.

Sercom pipeline stages map to Nutshell's deal stage pick-list. Each Sercom stage label is matched to the closest Nutshell stage; custom stages are created in Nutshell before the migration runs. Probability weights are assigned per stage based on Nutshell's defaults or your specified values.

Sercom engagement records (calls, emails, meetings) map to Nutshell Tasks and Events. Call records become Tasks with type='Call', meeting records become Events with start and end times. Original timestamps, owners, and associated contact/company links are preserved in the mapped Nutshell records.

Sercom notes are loaded into Nutshell Notes attached to the corresponding Person or Company record. File attachments are re-uploaded to Nutshell's file storage. Large attachments are handled within Nutshell's file size limits per upload, with migration logs tracking each file upload.

Sercom owner IDs are resolved by matching the owner email address against Nutshell user accounts. Unmatched owners are flagged before migration — your team either creates the Nutshell user or assigns the records to a fallback owner. No record lands in Nutshell without a valid user assignment.

Sercom custom fields on contact records are created as Nutshell custom fields on the Person tab before migration. Field type translation handles text, number, date, pick-list, and Boolean. Pick-list values are mapped one-by-one; new values are created in Nutshell if no match exists.

Sercom custom fields on account records are created as Nutshell custom fields on the Company tab. Field ordering and grouping are preserved as closely as the Nutshell schema allows. Validation rules that existed in Sercom must be rebuilt as Nutshell field validation in Settings.

Sercom custom fields on deal records are created as Nutshell Deal custom fields. Amount-based custom fields (e.g., contract value override) map directly to numeric fields in Nutshell. Multi-select pick-lists become single-select pick-lists unless Nutshell's settings allow multi-value storage on Deal custom fields.

Sercom workflows and automation rules do not migrate — they are platform-specific and have no equivalent structure in Nutshell. FlitStack AI exports workflow definitions as a reference document your team uses to rebuild them in Nutshell's automation builder.

Sercom reports and dashboards are not transferred. The underlying data (contacts, companies, deals, activities) migrates fully, so Nutshell's reporting tools can reconstruct the metrics your team tracks. Saved filter views in Sercom are documented for manual recreation in Nutshell.