Migrate from Visual Practice to Nutshell

Direct 1:1 map. Visual Practice person records migrate to Nutshell Person objects. The email field is the unique identifier — FlitStack uses it to detect duplicates and skip re-importing records that already exist in Nutshell. The mapping also preserves original create timestamps and owner assignments for each person record.

Direct 1:1 map. Visual Practice organization records migrate to Nutshell Organization objects. Parent-child organization hierarchies in Visual Practice are preserved using Nutshell's parent Organization lookup if the destination schema has been configured for hierarchical orgs. This ensures that organizational relationships are maintained and reporting structures remain intact after migration.

Visual Practice embeds the company reference on the person record. In Nutshell, persons link to organizations via a separate PersonLink object (Person.organization_id lookup). FlitStack resolves the organization ID first, then writes the person record with the correct lookup ID. The process also validates that the resolved organization exists before linking to avoid orphaned references.

Direct 1:1 map. Visual Practice leads migrate to Nutshell Leads. Status values (New, Contacted, Qualified, Unqualified) map to Nutshell's Lead status pick-list (New, Working, Bad) using a value-mapping table delivered in the migration plan. This mapping ensures that lead routing and follow-up workflows can be replicated accurately in Nutshell after the data transfer.

Visual Practice deals map to Nutshell Deals. Nutshell does not use a multi-stage pipeline model — the source deal stage (Prospecting, Proposal, Negotiation) maps to a custom deal stage field that Nutshell admins configure as a pick-list on the Deal object.

Direct map. Numeric deal value migrates to Nutshell Deal.value as a currency field. If Visual Practice stores value in a non-USD currency, FlitStack applies the exchange rate at migration time as a transformation step. The converted amount appears in the target Deal.value field, preserving historical deal size information for reporting and forecasting.

Visual Practice activities (calls, emails, meetings, notes) migrate to Nutshell Activities linked to the corresponding Person or Organization record. Original timestamps, activity type, duration, and owner are preserved in the migration. This ensures that the full communication history is available for follow-ups and audit trails in Nutshell.

Visual Practice file attachments on person, organization, or deal records are re-uploaded to Nutshell's file storage and linked back to the target record. Nutshell's file size limits apply — files exceeding the limit are flagged before the migration runs. The team can choose to exclude oversized files or host them externally to stay within Nutshell's storage constraints.

Visual Practice custom fields on Person records that have no direct Nutshell equivalent are created as custom fields on the Nutshell Person object before migration. FlitStack delivers a custom field creation plan specifying field name, type, and pick-list options. This plan also includes validation rules and default values to maintain data consistency after import.

Visual Practice deal-level custom fields (internal order numbers, custom priorities, deal sources) are created as custom fields on the Nutshell Deal object. Nutshell's allowed custom field types (Text, Number, Date, Choice, Checkbox) guide which type is used per field. Each custom field is also reviewed for pick-list options and any dependencies on other fields to ensure proper functionality after migration.

Visual Practice owner assignments on records resolve by email match against Nutshell user accounts. Unmatched owners are flagged before migration — the team either creates Nutshell accounts for them or assigns records to a fallback user. No record lands without a valid Nutshell owner.