Migrate from Evatic to Nutshell

Evatic stores customer contact records for service recipients. These map directly to Nutshell People records. Email, phone, name, and address fields transfer directly without transformation. Nutshell automatically flags duplicate email addresses during import, allowing your team to review and merge any potential duplicates before finalizing the migration.

Evatic's customer organizations map to Nutshell Companies. Company name, domain, address, and industry fields transfer directly. Parent-child organizational hierarchies in Evatic map to Nutshell's parent Company field if your Nutshell plan supports hierarchical company relationships. We verify plan capabilities during discovery.

Service agreement records carry contract value, start/end dates, and SLA terms. The contract monetary value maps to the Nutshell Deal amount field. The agreement status (active, expired, cancelled) maps to a custom pick-list field since Nutshell Deals use stage-based statuses.

Work orders represent discrete service events with technician assignment, date, and outcome. These translate to Nutshell Tasks: the service description becomes the task subject, the scheduled date becomes the due date, and the assigned technician maps to the Nutshell user owner by email match. Outcomes and notes migrate as task descriptions.

Evatic tracks equipment under contract as asset records with model numbers, serial numbers, and service history. These have no direct Nutshell equivalent. We migrate key equipment identifiers and service intervals as custom fields on the linked Company or Person record for reference.

Service agreements in Evatic typically contain multiple line items covering different service types, frequencies, and pricing tiers. We preserve this granular detail by migrating line item specifics as custom fields on the corresponding Nutshell Deal record, ensuring the full scope of contracted services remains visible without requiring a separate object structure in Nutshell.

Evatic tracks SLA compliance (response time, resolution time, first-contact resolution) per service agreement. These metrics have no Nutshell equivalent. We preserve SLA values as custom number fields on the linked Deal record so the service quality history is accessible post-migration.

Evatic technician records include names, certifications, and service areas. We resolve Evatic technician emails to Nutshell user accounts. If a technician does not have an email in Evatic, we flag that record for your admin to assign a fallback Nutshell user owner before migration.

Documents attached to Evatic work orders — including service reports, customer signatures, equipment photos, and completion certificates — re-upload as attachments on the corresponding Nutshell Activity. Nutshell natively supports file attachments on activities, so we re-upload and relink each document to preserve the complete audit trail and service history.

Evatic's automated dispatch rules and service area routing logic are configuration settings that have no Nutshell equivalent. These must be documented manually during a pre-migration audit and rebuilt as Nutshell assignment rules or workflow automations by your Nutshell admin following the migration. FlitStack exports workflow definitions as a reference document to accelerate the rebuild process.

Historical SLA breach events and escalation records in Evatic carry service quality history. We migrate the most recent breach date and escalation count as custom fields on the linked Nutshell Deal for reference, but the full escalation audit trail is preserved as a Note attachment.

Evatic generates invoices linked to service agreements. Nutshell does not have an invoicing object at the CRM level. Billing records and invoice history must be retained in Evatic or exported to a dedicated accounting tool — we do not migrate financial transaction records to Nutshell.