Migrate from Notifi to Nutshell

Notifi's customer contact (name, email, phone, address) maps directly to Nutshell's Person record. The primary service address from Notifi's job record is appended to the Person as a custom address field. All contacts migrate with their original create date preserved as a custom datetime field since Nutshell's created_at is set at import time.

Notifi's business customer record (company name, domain, industry, employee count) maps to Nutshell's Company object. Parent-child company hierarchies in Notifi map via Nutshell's Parent Company field. Multi-location business accounts are split into separate Nutshell Company records linked by a custom parent-reference field.

Notifi's Job is the core record type with no direct Nutshell equivalent — it becomes a Nutshell Deal. Job ID, status, priority flag, service type, and property class are stored as Nutshell custom fields on the Deal. The Deal name is constructed from the customer name + job type + date. Job technician assignment migrates as a custom Owner_Reference__c field (not a native Nutshell user lookup) since Notifi technicians may not have Nutshell user accounts.

Notifi job statuses (Scheduled, In Progress, Completed, Cancelled, On Hold) map to Nutshell Deal stages via a value-by-value table. We create a Nutshell pipeline called 'Field Service' with stages matching the Notifi status vocabulary. Stage-entry timestamps from Notifi become custom datetime fields on the Nutshell Deal for historical continuity.

Notifi Estimates contain line items with description, quantity, unit price, and total. Each unique line item description becomes a Nutshell Product record. The estimate total amount migrates as a custom Estimate_Total__c currency field on the linked Deal. Deposit amounts and accepted/rejected status are stored as separate custom fields on the Deal. Rejected estimates are stored as inactive Nutshell Products linked to the Deal for audit purposes.

Notifi recurring service plans (maintenance interval, next visit due date, subscription tier) have no native Nutshell equivalent. We create Service_Plan__c, Next_Service_Date__c, and Plan_Tier__c custom fields on the Nutshell Person record. Plan status (Active, Paused, Expired) migrates as a pick-list value in Plan_Tier__c. Recurrence frequency maps to a text field holding the interval description.

Notifi call logs and text message records map to Nutshell Tasks. The Task Subject carries the communication type ('Inbound Call', 'Outbound SMS'). Original timestamp, direction (inbound/outbound), duration (for calls), and technician attribution migrate as custom fields on the Nutshell Task. Call transcripts are not supported by Nutshell and are preserved as an attachment in the Nutshell record's file area.

Notifi invoices and payment receipts have no native Nutshell equivalent — Nutshell is a CRM, not an accounting platform. Invoice total, payment status, and payment method are stored as custom fields on the linked Nutshell Deal. The invoice PDF is saved as an attachment on the Deal record. For full financial history, a separate export of invoice data should feed into the accounting system.

Notifi allows custom fields on job records (property class, work category, urgency flag, etc.). Each Notifi custom job field requires a corresponding Nutshell custom field on the target object — we create these as Nutshell custom fields during the pre-migration schema setup phase. Field type mapping: Notifi text → Nutshell Text, pick-list → Nutshell Dropdown, date → Nutshell Date, checkbox → Nutshell Checkbox.

Notifi technician and admin users are resolved by email match against Nutshell Users. Notifi users with no matching Nutshell account are flagged before migration — you either create Nutshell accounts for them or assign their records to a fallback Nutshell user. Job history attribution (which technician completed a job) is preserved as a custom Technician_Name__c text field on the Deal since the native OwnerId may not correspond to a Nutshell user.

Notifi job photos and attached files are downloaded and re-uploaded to Nutshell Files linked to the corresponding Deal or Person record. File size limits apply — Nutshell handles files up to the platform default per upload. Very large photo sets are zipped before upload to reduce API call count.

Notifi routing rules, territory assignments, GPS-triggered notifications, and auto-assignment workflows are not accessible via API. They cannot be migrated. We export a structured JSON document describing every active Notifi workflow (trigger conditions, actions, filters) as a reference for rebuilding in Nutshell's automation tools or a separate workflow engine.