Migrate from Vortex Field Software to Nutshell

Vortex Work Orders map to Nutshell Deals as the primary opportunity record. The work order name becomes the Deal name, amount reflects total service value, and stage is set to a custom pipeline stage mapped from Vortex status. Service context (technician, asset, SLA tier) is preserved as custom fields on the Deal.

Vortex Assets — representing equipment, locations, or service sites — map to Nutshell Companies. Asset name becomes the Company name, address maps to the Company address fields, and asset serial number and type are stored as custom fields on the Nutshell Company record for reference and reconciliation.

Vortex customer contact records (name, email, phone, company association) map directly to Nutshell Person records. The Person is linked to the corresponding Nutshell Company derived from the Vortex asset, preserving the asset-contact relationship within Nutshell's association model, and each Person retains the original contact address and communication preferences for follow-up activities.

Vortex Technicians are internal users, not external contacts. They are matched to Nutshell Users by email address — if a Nutshell User account exists, the technician record links directly for owner assignment on Deals. If no matching user exists, the technician name is stored as a custom field on the Deal for reference.

Vortex Service History entries — including completed work, parts used, labor hours, and customer sign-offs — are converted to Nutshell Notes attached to the corresponding Deal. Each Note preserves the original timestamp, technician name, and service narrative so the full job history is queryable in Nutshell.

Vortex work order line items (parts, labor, travel) do not map to a native Nutshell object. FlitStack merges line-item data into a structured text field or set of custom fields on the Deal — labor hours, parts cost, and total amount as separate numeric fields, parts list as a text block — so the financial detail is preserved without creating sub-records.

Vortex contract and SLA tier information attached to work orders has no native Nutshell equivalent. FlitStack creates custom pick-list fields on the Deal for SLA tier (Gold, Silver, Bronze) and stores contract start and end dates as custom date fields for SLA compliance tracking.

Vortex asset type classifications (HVAC, Electrical, Plumbing, etc.) are mapped to Nutshell Company tags for filtering and reporting. Where teams use a predefined taxonomy, FlitStack creates a Company pick-list custom field to preserve the full classification set from Vortex, and enables segmentation based on service categories for targeted marketing and service routing.

Vortex scheduling records showing technician assignment and scheduled date-time map to Nutshell Tasks on the corresponding Deal. The task subject references the work order name, due date reflects the scheduled service date, and the assigned Nutshell User is populated from the technician email match.

Vortex file attachments on work orders — including signed service forms, equipment photos, and inspection reports — are downloaded from Vortex and re-uploaded to Nutshell as Files linked to the corresponding Deal. Files are stored with the original filename and upload timestamp preserved.

Vortex custom fields not covered by standard mappings (certification levels, billing codes, internal tracking IDs) are created as custom fields on the appropriate Nutshell object (Person, Company, or Deal) using the same field type. Pick-list custom fields in Vortex replicate as pick-list custom fields in Nutshell.