Migrate from MOGO to Nutshell

MOGO person records map 1:1 to Nutshell People. Fields including name, email, phone, and address carry over directly. MOGO owner email resolves to a matching Nutshell user by email — unresolved owners are flagged before migration commits any records. This resolution ensures that record accountability and assignment history are preserved accurately in Nutshell.

MOGO organization or company records map to Nutshell Companies. Company name, website, industry, and employee count translate to Nutshell's corresponding fields. MOGO's company hierarchy (parent-child) maps to Nutshell's parent company lookup if configured. This mapping preserves organizational structures and allows teams to view accounts with their hierarchical relationships intact after migration.

MOGO deal records map to Nutshell Deals with deal name, amount, stage, and expected close date. MOGO's deal stage names map value-by-value to Nutshell stage names. Stage probability values are reapplied based on Nutshell's stage configuration after mapping. This ensures deal forecasting and pipeline reporting work accurately using Nutshell's native probability calculations.

If MOGO uses multiple deal pipelines, each MOGO pipeline maps to a separate Nutshell Pipeline. Nutshell's pipeline builder lets you configure stages, probability weights, and automation triggers per pipeline — the mapping plan includes the configuration for each. This approach maintains complete pipeline continuity and allows teams to work with familiar sales processes immediately after migration.

MOGO call logs, email records, meetings, and notes map to Nutshell's corresponding activity types (Call, Email, Meeting, Task). Original timestamps, owners, and the parent record link (person or deal) are preserved. Activities without a parent are linked to the associated Person if a link exists.

MOGO custom fields on People, Companies, and Deals require Nutshell custom fields to be created in advance in Settings > Custom Fields per entity. We deliver a custom field creation plan specifying field name, type (text, number, date, picklist), and which MOGO values map to each Nutshell field. Fields that have no Nutshell equivalent are preserved as custom fields for reference.

MOGO owner or assigned-user records resolve against Nutshell users by email address match. MOGO records with owners who have no matching Nutshell user are assigned to a designated fallback owner and flagged in the migration report for manual reassignment. This ensures every record has an accountable owner in Nutshell while giving your team visibility into any unresolved assignments that need attention.

MOGO file attachments associated with person or deal records are downloaded and re-uploaded to Nutshell. Files are attached to the corresponding Nutshell Person or Deal record. File size limits follow Nutshell's storage policy for your plan tier. All file metadata including original upload dates and file types are preserved to maintain complete document history and audit trails.

MOGO leads that are not yet converted to contacts map to Nutshell Leads. Lead status, source, and rating map to Nutshell's lead fields. Leads converted in MOGO before migration are treated as People in Nutshell to avoid duplicate records. This prevents duplicate contact creation and ensures your lead pipeline history is fully accessible in Nutshell's lead management interface.

MOGO tasks and reminders map to Nutshell Tasks with subject, due date, assignee, and status. Completed and open tasks both migrate. Tasks linked to a MOGO person or deal carry the parent record reference to the corresponding Nutshell entity. This preserves task accountability and ensures your team can track outstanding work items immediately after migration without losing context.