Migrate from MarketSharp to Nutshell

MarketSharp Custom Lead Fields do not auto-create in Nutshell — manual setup required before migration

MarketSharp Custom Lead Fields are account-specific configurations created under Settings → Custom Lead Fields. Nutshell requires its own custom field setup via Settings → Custom Fields on each object type (People, Companies, Leads). We cannot auto-provision Nutshell custom fields via API — your Nutshell admin must create matching custom fields before the migration run. We deliver a custom field creation guide based on your MarketSharp field inventory so the setup takes under an hour. Migration will skip any MarketSharp custom field that doesn't have a corresponding Nutshell destination field, flagging them for post-migration review.

MarketSharp Jobs and Project Data have no native Nutshell equivalent

MarketSharp includes job costing, production management, and QuickBooks Connector features that are outside Nutshell's scope as a CRM. Nutshell has no Job or Project object — the closest analog is a Deal with custom fields, but that requires a custom object setup on the Nutshell side before migration. We surface MarketSharp Jobs as activity notes on the linked Company/Person, preserving job number, status, and value. If you need structured job tracking in Nutshell, that requires a custom object setup that is outside the standard migration scope and scoped as additional work.

Appointment metadata (crew, product, address details) flattens into Nutshell activity notes

MarketSharp Appointments have structured fields for salesperson, crew members, product type, and job site address. Nutshell Activities are freeform Tasks and Events with no equivalent structured schema. We transfer appointment datetime, duration, and notes, but MarketSharp's crew assignments and product fields append to the activity notes as text. This means crew-specific assignment tracking that exists in MarketSharp will not be queryable in Nutshell reports — it becomes a note string. Plan to rebuild appointment-type workflows using Nutshell Tasks if crew-level reporting is needed.

MarketSharp workflows and automation rules do not transfer to Nutshell

MarketSharp automations (email sequences, task triggers, lead routing rules) are platform-specific and cannot be exported in a transferable format. Nutshell's automation tools (Personal Email Sequences, Task automation, lead routing) require manual rebuild. We export your MarketSharp workflow definitions as a structured document that your Nutshell admin can use as a rebuild reference. This is always a manual step — no automated conversion exists between the two platforms' automation engines. Budget 2–5 hours per complex workflow for rebuild time.

Owner email resolution may leave records unassigned if Nutshell users don't exist

MarketSharp salespeople are matched to Nutshell users by email address. If a MarketSharp owner email doesn't correspond to an existing Nutshell user at migration time, their records are flagged as 'unassigned' and held from the migration run. Your team must either create the corresponding Nutshell user before migration or define a fallback owner assignment rule. We run a pre-flight owner audit 48 hours before migration to surface these mismatches so they can be resolved before data moves.