Migrate from Upvise to Nutshell

Upvise Contacts map directly to Nutshell People. Name, email, phone, address, and job title fields transfer to matching Nutshell Person fields. The original Upvise contact ID is preserved as Source_System_ID__c for delta-run deduplication. This custom field enables FlitStack to identify previously migrated contacts during subsequent delta runs, preventing duplicate record creation and ensuring data integrity throughout the migration lifecycle.

Upvise Contacts flagged as prospects (role field = 'prospect' or 'lead') route to Nutshell Leads during migration. Status values map to Nutshell Lead Status pick-list entries. Contacts with role='customer' or 'client' remain as Nutshell People. Any contact records lacking a role designation are flagged for manual review before the full migration executes, ensuring clean segmentation between qualified and unqualified prospects in the target system.

Upvise Companies map 1:1 to Nutshell Companies. Name, domain, industry, employee count, and annual revenue fields transfer directly. Parent-child company hierarchies in Upvise map to Nutshell's parent company reference field. The original company creation timestamp is preserved in a custom datetime field to maintain historical accuracy for reporting and audit purposes in Nutshell.

Upvise Jobs translate to Nutshell Deals. Job name, amount, and status become Deal name, value, and pipeline stage respectively. The job's primary Contact and Company become the Deal's linked Person and Company in Nutshell. Custom fields attached to the Upvise Job migrate to the corresponding Deal's custom fields, maintaining all job-specific data properties in the new system.

Upvise job status values (e.g., Quoted, In Progress, Won, Lost) map to Nutshell Pipeline Stage pick-list values. Each Upvise status gets assigned a corresponding Nutshell stage; teams with multiple distinct statuses may require multiple Nutshell pipelines for correct scoping. The value mapping table is reviewed during the sample migration phase to ensure accurate stage attribution before the full run.

If Upvise Jobs use a Jobtype field to distinguish deal categories (e.g., 'Service' vs. 'Product'), FlitStack creates separate Nutshell Pipelines keyed by that field. Each pipeline gets its own stage set, ensuring stage pick-list values are scoped correctly. This approach prevents stage value conflicts across different job categories and aligns with Nutshell's pipeline architecture for accurate pipeline reporting.

Upvise Custom Fields attached to Jobs become Nutshell custom fields on the Deal object. Field types (dropdown, date, checkbox) map to Nutshell's equivalent types. For per-pipeline custom fields, the field is scoped to the pipeline that received the job's data.

Upvise Contact-level custom fields migrate as Nutshell custom fields on the Person object. Field types including text, number, date, and dropdown map to Nutshell's corresponding field types. If the original contact was classified as a Lead during the split migration, the custom field migrates to the Lead record as well, preserving reporting continuity across both Person and Lead objects in Nutshell.

Upvise Company-level custom fields transfer to Nutshell Company custom fields. The field name in Upvise becomes the display label in Nutshell; the API name is auto-generated by Nutshell's field creation process. All company-specific data properties remain intact, allowing teams to maintain detailed company profiles in the new CRM without manual re-entry.

Upvise activity records attach to Jobs and migrate as Nutshell Activities. Call activities become Nutshell Tasks with Type='Call'. Note activities become Nutshell Notes. Email logging migrates as Task activities with Type='Email'. Original timestamp and owner attribution are preserved on each activity record, maintaining the complete activity history timeline in Nutshell for account management and audit trails.

Upvise user IDs are resolved by email match against Nutshell users before migration. FlitStack compares each Upvise owner's email address with Nutshell user accounts to establish the correct OwnerId mapping. Unmatched owners receive a fallback assignment to a designated Nutshell admin. The original owner ID from Upvise is logged in Source_Owner_ID__c for post-migration auditing and reporting accuracy.

Files attached to Upvise Jobs or Contacts are downloaded and re-uploaded to Nutshell as Attachments linked to the corresponding record. File size limits from Nutshell's storage configuration apply; large files may require compression. All attachment types including documents, images, and PDFs transfer to maintain complete record context in Nutshell's activity timeline.

Upvise Assets have no direct Nutshell equivalent in standard plans. If your team relies on asset tracking, the asset records migrate as a custom object in Nutshell (requires Enterprise plan). Asset-to-Job relationships are preserved as custom lookup fields on the custom object, allowing you to link asset records to Deals. This ensures asset context is maintained even without native asset management in Nutshell.

Upvise workflow automations and form scripts do not migrate due to platform-specific implementation differences. FlitStack exports complete workflow definitions as JSON for reference documentation. Nutshell's own automation builder (available on Pro+ tiers) must be used to recreate these workflows post-migration. The exported JSON provides a detailed blueprint for rebuilding each automation step-by-step in Nutshell's workflow engine.