Migrate from Moskit to Nutshell

Moskit Contact records map directly to Nutshell Person. Standard fields (name, email, phone, address) transfer via field-name mapping. Any Portuguese custom field labels on Contact (e.g., campos_personalizados) are preserved as-is and documented in a translation glossary included with the migration package. If a Contact has multiple phone types (Celular, Telefone Comercial), we map these to Nutshell's phone and additional_phones array structure.

Moskit Empresas map to Nutshell Accounts. The company's CNPJ or business registration number, if stored in a custom field, maps to a Nutshell custom text field. We create the Account before importing any linked Contacts so that the Account lookup is satisfied at Contact insert time. If the Moskit account has multiple associated contacts, all contacts reference the same Account ID.

Moskit Deals map to Nutshell Deals with pipeline stage, monetary value, expected close date, owner, and custom fields. The deal's pipeline name maps to Nutshell's pipeline configuration. We pre-create the Nutshell pipeline and stage structure before migration so that stage values resolve correctly on import. Closed-won and closed-lost reasons migrate as custom fields if they exist in Moskit.

Moskit pipeline stages (e.g., Qualificação, Proposta, Fechado Ganho) are mapped to Nutshell stage names that the customer configures before import. Stage order and probability percentages transfer as configuration. If Moskit has multiple deal pipelines, we create multiple Nutshell pipelines or use Nutshell's multiple pipeline capability (Pro tier and above) for the mapping.

Moskit Activities of type call, email, meeting, and task map to Nutshell Activity records with the matching type. Activity description, timestamp, owner, and linked Contact or Deal references transfer. Note-type activities map to Nutshell notes attached to the parent Person, Account, or Deal. We preserve activity ordering by timestamp so the activity timeline reads chronologically in Nutshell.

Moskit Projects are deal-linked and contain task, date, and assignment data. Nutshell has no native project object. We discuss two options with the customer during scoping: map Projects to Nutshell Accounts using a project-name Account and project tasks as Activities, or map them to Deals using a custom deal stage as a project bucket. The choice depends on how the customer uses Projects. Project-to-deal linkage is preserved as a custom reference field we create in Nutshell (e.g., moskit_project_id__c) for audit.

Moskit custom fields on Contacts, Companies, Deals, and Activities are extracted per object type (Moskit has no bulk schema enumeration endpoint, so we query each object type individually). We create matching Nutshell custom fields before migration, type-mapped (text to text, number to number, date to date, picklist to picklist). Portuguese option labels in Moskit picklist fields are preserved as-is in Nutshell unless the customer requests translation.

Moskit Users map to Nutshell Users by email match. We extract all active and inactive users from Moskit with their role and owner assignments. Inactive Moskit users are migrated as inactive Nutshell users with a deactivation flag so the customer's admin can manage provisioning. Any Moskit user without a matching Nutshell user goes to a reconciliation queue for the admin to provision before record import resumes.

Moskit pipeline configurations (pipeline name, stages, stage order, probability percentages) transfer to Nutshell pipeline configuration. Nutshell's pipeline capability scales with tier: Foundation uses a single default pipeline; Pro supports up to 5 pipelines; Business and Enterprise support unlimited pipelines. We configure Nutshell pipelines before record migration begins.