Migrate from Allegory to Nutshell

Allegory contacts map directly to Nutshell People. Nutshell People store name, email, phone, address, and custom fields. A primary company association migrates as the AccountId link; contacts without a company land in Nutshell without an account association and can be linked manually post-migration.

Allegory companies map to Nutshell Accounts. Account stores company name, website, industry, employee count, revenue, and custom fields. Nutshell Accounts support parent-child hierarchies using a parent_account_id field — we map Allegory's parent company link accordingly. We also preserve the original Allegory company ID as a custom field for cross-referencing and audit trails.

Allegory deals map to Nutshell Deals with full pipeline stage mapping. Each Allegory deal stage maps to a corresponding Nutshell deal stage — we build the stage mapping table during planning. Deal amount, close date, owner, and custom fields migrate directly. Nutshell's deal list supports list, map, chart, and board views.

Allegory leads map 1:1 to Nutshell Leads. Lead status, source, owner, and custom fields migrate. Leads in Allegory that are already converted require a flag in the Nutshell Lead indicating the conversion status and related Person/Deal references. If a lead is attached to a converted Person, we store the original Allegory contact ID on the Nutshell Lead record for reconciliation.

Allegory tasks map to Nutshell Activities with Type='Task'. Original due date, description, owner, and status (completed/pending) migrate. Completed tasks preserve the completion timestamp; open tasks preserve the due date. If Allegory tasks have a priority field, we map it to a custom Nutshell text field so managers can sort by priority in reports.

Allegory call logs map to Nutshell Activities with Type='Call'. Duration, outcome (answered, voicemail, no answer), notes, and timestamp migrate. Call owner resolves by email match to a Nutshell user. If Allegory records include a call disposition code, we store it as a custom text field on the Nutshell Activity for downstream reporting.

Allegory email logs migrate as Nutshell Activities with Type='Email'. Subject, body, direction (sent/received), timestamp, and owner migrate. Email thread linking depends on Allegory's thread ID — if present, we surface it as a custom field in Nutshell for manual thread reconstruction.

Allegory meeting records migrate to Nutshell Activities with Type='Meeting'. Start time, end time, location, attendees (as notes), and owner migrate. Recurring meetings from Allegory expand into individual Nutshell Activity records with a recurrence reference field. If the Allegory meeting includes an organizer field, we map it to the Nutshell Activity owner to preserve attribution.

Allegory notes on contacts or companies migrate as Nutshell Activities with Type='Note'. Note body and timestamp migrate. Rich-text formatting is preserved where Allegory supports it — plain text where it does not. If the note contains any @mentions of other users, we preserve the mention text as a custom field for follow-up.

File attachments on Allegory contacts, companies, or deals re-upload to Nutshell as file attachments on the corresponding record. File size limits apply per Nutshell's attachment handling — we flag any files exceeding Nutshell's supported size before the run. We also log the original Allegory file ID in a custom field to assist with any post-migration file audit.

Allegory custom objects map 1:1 to Nutshell custom objects if they exist in the Nutshell account. Custom object associations using N:N relationships in Allegory need junction objects in Nutshell — we document this in the migration plan and let you decide whether to rebuild the association logic.

Allegory users and deal owners resolve by email match against Nutshell users. Unmatched owners are flagged before migration — your team either creates the Nutshell user first or assigns their records to a designated fallback user. No record lands without a valid Nutshell owner.