Migrate from Powered Now to Nutshell

Nutshell has no native job or field-service data model

Powered Now's entire value proposition is tracking jobs end-to-end: scheduling, technician assignment, status per job, quotes and invoices per job. Nutshell is a sales CRM — its native objects are People, Companies, Leads, Deals, and Tasks. Jobs cannot map to a single native Nutshell object; they become Deals with a cluster of custom fields (Job_Scheduled_Date__c, Technician__c, Job_Status__c, Job_Description__c) that preserve the Powered Now job semantics without native support. This is not a limitation FlitStack can bypass — it is a structural difference between the platforms that affects how your team will use Nutshell after migration.

Quote and invoice PDFs migrate as attachments, not native records

Nutshell has no native quote or invoice object. Powered Now quotes and invoices cannot map to a structured Nutshell record — they are PDFs that we re-upload as file attachments on the corresponding Deal. This means quote line items, invoice totals, and payment history are not queryable as fields in Nutshell. We add a custom Invoice_Status__c pick-list and capture the monetary amount in Deal value, but the full financial document lives in the file attachment. If your team needs to query invoice status in reports, plan to build custom reporting on the custom field or export the attachment metadata separately.

Scheduling data requires a custom-date field on Deals

Powered Now's diary and scheduling engine tracks which technician is assigned to a job and on what date. Nutshell's pipeline Stages do not function as scheduling slots, and Nutshell has no native diary or resource-management module. We create a custom field Job_Scheduled_Date__c on Deals to carry the original scheduled date, and Technician__c as a text field for the assigned technician. These fields are visible in the Deal record and can be included in Nutshell's list views, but they do not appear in the native pipeline board in a way that mirrors Powered Now's diary view.

Workflows and automations do not migrate — rebuild required

Powered Now automations (certificate reminders, job-routing triggers, form auto-fills, VAT compliance alerts) are built on Powered Now's own automation engine and have no equivalent structure in Nutshell. They cannot be migrated in any automated sense. FlitStack exports the Powered Now workflow definitions as a structured JSON reference document. Your Nutshell admin uses this to rebuild equivalent rules in Nutshell's workflow builder (Settings > Workflows). Budget time for this rebuild — it typically takes 4–10 hours depending on automation complexity, and it is not included in the standard migration fee.

Multi-address clients require multiple Deal records or manual de-duplication

A Powered Now client may have multiple job addresses across the UK — a primary site, a billing address, and one or more service locations. Nutshell People and Companies have a single address field. We migrate the primary address on the Person record and attach additional addresses as a custom text field (Additional_Addresses__c). Each job's specific address is preserved in the Job_Description__c custom field on the corresponding Deal. If you need all addresses to map cleanly, consider creating separate Company records per address — but this introduces de-duplication complexity that your admin should review during the planning phase.