Migrate from Ascora to Nutshell

Nutshell has no native job-status or field-service object — job status requires custom field creation

Ascora jobs carry a status workflow (Pending, In Progress, On Hold, Complete) that Nutshell does not model natively. Nutshell's Deal object has a pipeline stage but no field-service status concept. We create a Job_Status__c custom pick-list field on Deals and map each Ascora status value to it. If your team relies on status reporting in Ascora (e.g., jobs currently In Progress), that same report needs to be rebuilt in Nutshell using the Job_Status__c custom field as the filter — Nutshell's native pipeline reporting uses stage, not a job-status pick-list. Pre-creating Job_Status__c before migration ensures the field exists at load time and avoids a post-migration field-addition cycle.

Scheduling and technician dispatch do not exist in Nutshell and cannot be migrated

Ascora's drag-and-drop scheduler, crew assignment, and real-time GPS routing are core to its field-service functionality. Nutshell has no scheduling module — its mobile app supports task updates and activity logging but not job dispatch or crew calendars. When we migrate a job to a Nutshell Deal, the assigned technician becomes the Deal owner and the technician name is stored as Technician__c, but the scheduling layer (job start time, route sequence, travel time) does not transfer. Teams using Ascora's scheduling must rebuild that capability in a dedicated field-service tool (e.g., Jobber, Housecall Pro) or use Nutshell Tasks with manual assignment. We export Ascora's schedule data as a CSV reference file for the rebuild.

Quote and invoice objects in Ascora have no Nutshell equivalent — line items and tax data require attachment-based preservation

Ascora treats quotes and invoices as first-class objects with line items, tax rates, discounts, and payment terms. Nutshell has no native quote or invoice object — proposals can be attached as files, and invoice references are stored as custom fields. We map the quote total, invoice number, total amount, and payment status to custom fields on the Deal, and attach the exported PDF of each quote and invoice as a Nutshell File. The line-item detail (individual products, quantities, unit prices, tax breakdown) is only preserved inside the PDF attachment, not as structured fields. If your team needs to query invoice totals or payment status by line item in Nutshell reports, that requires a custom report type or an external BI tool — it cannot be built with Nutshell's standard reporting.

Nutshell contact-based pricing tiers affect total migration cost if customer count is large

Nutshell's pricing scales by contact count (People records) on the account. Ascora's customer export may include inactive or archival records that inflate the count. We work with your team before migration to define inclusion criteria — active customers only, records modified within a date range, or excluding test records — to avoid landing on a pricing tier higher than necessary. Nutshell plans range from Foundation ($13/user/month with 100 contact limit) to Enterprise ($79/user/month with 500,000+ contact ceiling). If your Ascora export exceeds 100 contacts and you are targeting a low-tier plan, we can flag the count implications and suggest archiving inactive records before migration.