Migrate from Convert Wire to Nutshell

Convert Wire's Person records map directly to Nutshell People. Email, phone, job title, address fields, and custom properties transfer as-is. Original create and update timestamps are preserved as custom datetime fields since Nutshell sets the system CreatedDate at migration time. This preservation maintains historical reporting continuity and allows teams to track record age in Nutshell after migration.

Convert Wire Company records map directly to Nutshell Companies. Standard fields including company name, domain/website, industry classification, employee count, annual revenue, and address information transfer as-is. Any custom fields on Company records also map to Nutshell Company custom fields. Parent-company hierarchies map using Nutshell's parent_company association field, which requires the parent company to exist in Nutshell before the child record migrates. Circular references are flagged and resolved before migration runs.

Convert Wire leads (unqualified prospects not yet converted to Person records) map to Nutshell Leads. Lead status, source, score, and custom fields transfer directly. Nutshell Leads have a separate field set from People records—custom field mapping must account for this distinction since a field available on Convert Wire Person may not exist on Nutshell Lead without custom field creation. FlitStack audits the field schema for both record types before migration to ensure all applicable fields transfer correctly.

Convert Wire Deals map to Nutshell Deals with direct field mapping for deal name, amount, stage, probability, expected close date, and owner. Stage names map value-by-value to corresponding Nutshell stage names—FlitStack reviews your Convert Wire stage configuration and creates matching stages in Nutshell before migration. Loss and won statuses align with Nutshell's closed-won/closed-lost model. If your Convert Wire pipeline includes stages not present in Nutshell's default configuration, custom stage creation is required prior to the migration run.

Nutshell uses a single unified pipeline model for all deals, unlike Convert Wire which may support multiple independent pipelines. If Convert Wire has multiple pipelines, they collapse into one Nutshell pipeline during migration. To preserve visibility into original pipeline origin, FlitStack maps the source pipeline name to a custom text field (Original_Pipeline__c) on each Deal. Teams requiring strict pipeline separation in Nutshell should use tags, custom fields, or separate Nutshell workspaces to simulate pipeline segmentation, which requires planning before migration.

Convert Wire activity records (calls, emails, meetings, tasks) map to Nutshell Tasks and Events. Call logs transfer as Tasks with Type='Call'. Meetings transfer as Events with start/end times. Emails map as Tasks with subject and body preserved. Original timestamps and owner assignments carry over.

Convert Wire notes attach to Person, Company, or Deal records and map directly to Nutshell Notes. Rich-text formatting including bold, italic, lists, and hyperlinks is preserved where the source format is compatible with Nutshell's note format. Notes include the original create datetime and author attribution to maintain complete audit trails in the destination system. If a Convert Wire note contains formatting not supported by Nutshell, FlitStack converts it to plain text with the original content intact.

File attachments on Convert Wire records—typically on Deals, Companies, and sometimes People—re-upload to Nutshell's file attachment system via Nutshell's API. Files must be downloaded from Convert Wire's storage and re-hosted in Nutshell's file storage during migration. Nutshell enforces file size limits for attachments, and files exceeding these limits require alternative handling such as linking to external storage. FlitStack identifies files that may exceed size limits before migration so teams can plan accordingly.

Convert Wire custom fields on Person records that have no direct Nutshell equivalent require custom field creation in Nutshell before migration begins. FlitStack audits the custom field inventory during the schema review phase and creates all required fields via Nutshell's API. Supported field types include text, number, date, phone, URL, single-select picklist, and multi-select picklist—all of which have Nutshell custom field equivalents. Multi-select fields without a native Nutshell equivalent are serialized as comma-separated text for migration, with native multi-select recreation planned post-migration.

Custom fields on Convert Wire Company records map to Nutshell Company custom fields, following the same creation process as Person custom fields. Multi-select fields use Nutshell's native multi-select type where available for direct mapping. For multi-select fields without a Nutshell equivalent, FlitStack serializes the selected values as comma-separated text in a custom text field, preserving all selected values. Teams requiring true multi-select filtering in Nutshell should plan to recreate these fields as native multi-select post-migration based on the serialized data.

Deal-level custom fields in Convert Wire—such as internal order numbers, deal sources, custom probability overrides, and deal-specific tracking fields—map to Nutshell Deal custom fields. FlitStack creates all required Deal custom fields in Nutshell via API during the schema setup phase. Standard field types like text, number, and date map directly, while custom picklists require value mapping between Convert Wire and Nutshell options. All Deal custom fields must exist in Nutshell before the migration run to prevent data loss during the transfer.

Convert Wire user records resolve to Nutshell users by email address match. If a Convert Wire owner has no corresponding Nutshell user, their records assign to a designated fallback user. Unmatched owners are flagged before migration so the team can provision Nutshell accounts first.

Workflows, sequences, and automation rules do not transfer. Convert Wire workflow definitions export as JSON documents for manual rebuild in Nutshell's automation builder (available on Pro+ plans). This is a manual step that the FlitStack team coordinates with your Nutshell admin.