Migrate from Urban-Hawks to Nutshell

Urban Hawks Companies map directly to Nutshell Accounts — the name, domain, address, and industry fields carry over. Multi-branch companies in Urban Hawks with child locations need to be flattened or linked via Nutshell's custom fields if hierarchical reporting is required, since Nutshell Accounts do not support a native parent-child hierarchy.

Urban Hawks Contacts migrate to Nutshell People using direct field mapping for name, email, phone, and address. The primary Company association on the Contact becomes the primary AccountId on the Nutshell Person. Additional company associations on the Urban Hawks Contact require Account Contact Relationships in Nutshell, which we set up during the migration.

Work Orders have no native equivalent in Nutshell's CRM model. FlitStack AI converts each Work Order into a Nutshell Deal with the work order name as the deal name, the assigned technician as the deal owner, and the work order description and resolution notes added as Nutshell Activities under that deal. The original work order status maps to a Nutshell deal stage (e.g., Scheduled, In Progress, Completed).

Urban Hawks line items on work orders (parts used, service codes, labor hours) do not map to any standard Nutshell field. We create a Nutshell custom field on the Deal to capture the service line summary, or embed the full line-item detail in the deal description field — your team chooses the preferred format during the sample migration review.

Urban Hawks Locations (site addresses separate from the Company address) have no native Nutshell equivalent. We map the primary site address to a Nutshell Account address and create a custom Account-level text field to hold the full location list when multiple sites are involved. Field-visit history attaches as Activities on the relevant Deal.

Urban Hawks Asset records (equipment tracked per location) store serial numbers, install dates, and service history. Nutshell has no Asset object. We migrate asset serial numbers and install dates to Nutshell Account custom fields, and embed the service history as an Activity note on the associated Deal so the full service record is accessible without leaving the CRM.

Urban Hawks technician records represent field employees who own Work Orders. Nutshell Users represent CRM users who own Deals, People, and Leads. FlitStack AI resolves Urban Hawks technician emails against existing Nutshell users and flags unmatched technicians — your team either creates Nutshell user accounts for them or assigns their records to a designated fallback owner.

Urban Hawks billing contacts stored as separate Contact records migrate to Nutshell People linked to the same Account. If the billing contact is distinct from the field contact, both Person records are created and associated with the Account. Primary billing flag stored as a custom Person-level field in Nutshell.

Urban Hawks file attachments on Work Orders and Contacts re-upload to Nutshell as attachments on the corresponding Deal or Person. Nutshell supports file attachments on Deals and People. Large file attachments (exceeding Nutshell's size limits) are flagged during the sample migration so your team can decide whether to migrate them or store them externally.

Urban Hawks scheduling events (time slots, route assignments, dispatch windows) have no native Nutshell equivalent. We preserve the scheduling data as a custom note on the associated Deal, tagged with the original dispatch timestamp and assigned technician. Calendar sync and route-based scheduling require Nutshell's third-party integrations or a rebuild outside the CRM.

Urban Hawks extended properties on any entity map to Nutshell custom fields on the equivalent entity. Nutshell allows custom fields on Accounts, People, and Leads. Custom fields on Deals or Activities are not available in standard Nutshell — for these, we embed the data in the deal name, description, or an activity note, flagged with the original field label for reference.