Migrate from myCRMS.com to Nutshell

myCRMS.com Contact records map directly to Nutshell Contact. The mapping uses email as the primary dedupe key. If the source export exposes custom fields, we create corresponding custom fields in Nutshell during the pre-migration schema audit. Note that Nutshell's UI refers to contacts as 'People' while the API uses 'Contacts'; we use the API terminology for the mapping. AccountId is resolved from the company lookup before contact insert so that the relationship is satisfied at load time.

myCRMS.com Company records map to Nutshell Account. The domain or website field from myCRMS.com becomes the Account's website field in Nutshell. Account is loaded before any Contact records to satisfy the lookup relationship. If the source export exposes industry, employee, or revenue fields, those map to standard Nutshell Account fields or custom fields created during schema setup.

myCRMS.com Deals map to Nutshell Opportunity. The deal stage property maps to a Nutshell pipeline stage. If myCRMS.com exposes multiple pipelines, each becomes a separate Nutshell pipeline with its own stage sequence. Closed-won and closed-lost dates migrate as Opportunity close date and status. OwnerId resolves from the email-to-user lookup.

Each distinct myCRMS.com pipeline becomes a Nutshell pipeline. We configure the pipeline stages in Nutshell before migration, mapping each source stage name to the equivalent Nutshell stage. Stage probability values from myCRMS.com, if available in the export, are set on the corresponding Nutshell stages. This step requires a scoping call to confirm how many distinct pipelines exist in the source.

myCRMS.com Smart Lists are filtered contact groups documented during the pre-migration audit. We do not migrate Smart Lists as code because the filter logic (field conditions, operators, and combinators) may not export cleanly. Instead, we deliver a written inventory of each Smart List with its filter structure and recommended Nutshell Saved View equivalent. The customer's admin rebuilds the Saved Views in Nutshell post-migration using the inventory as a guide.

myCRMS.com Owner assignments on Contact, Company, and Deal records map to Nutshell User records resolved by email match. Owners without a matching Nutshell User are flagged in a reconciliation report and held until the customer's admin provisions the missing User or assigns an alternative. Migration cannot proceed past deal import until all Owner references resolve because OwnerId is required on Opportunity in Nutshell.

myCRMS.com activity records with timestamps migrate to Nutshell Task (for calls and tasks) and Event (for meetings). Email history migrates to Nutshell Task records with the email content body preserved if the source export exposes it. ActivityDate and duration fields map to Nutshell standard fields. We use Nutshell's JSON-RPC API with batch sizing and exponential backoff to respect rate limits on find requests. If the source export does not expose activity timestamps, we flag this gap in the pre-migration audit and note that engagement history cannot be reconstructed from the export.

Custom fields discovered during the pre-migration schema audit are created in Nutshell before any data loads. Field types map to equivalent Nutshell custom field types (text, number, date, dropdown). We do not assume a uniform custom field structure; each myCRMS.com account may have a different schema. The audit phase establishes the exact field list and types before the migration script is written.