Migrate from Urban-Hawks to Zoho CRM

Urban Hawks technician records (name, email, phone, certifications, device_type) map to Zoho CRM Users for login access and to Contacts for service-history association. Certified technician status migrates as a custom pick-list field (Technician_Certification__c) on the Contact record. Technician ID values are preserved as the Zoho User external ID to enable future sync operations between Urban Hawks and Zoho.

Urban Hawks equipment records map to Zoho CRM Accounts as the primary entity, with an optional custom Equipment module linked via Account lookup when detailed asset tracking (serial number, install_date, warranty_expiry) is required. The account name holds the equipment description; the equipment serial number becomes a custom field.

Urban Hawks links between service assets and customer accounts (which asset belongs to which customer) map to Zoho Account Contact Relationships. This preserves the many-to-one relationship model where a single customer may have multiple installed assets. Each asset record retains a reference to its owning customer account, and the relationship is exposed in Zoho via the Account's related list of linked assets.

Urban Hawks work orders map directly to Zoho CRM Deals (Potentials). Work-order number becomes the Deal name with original create date preserved as a custom datetime field. Deal stage (Open, In Progress, Resolved) maps to Zoho Deal stage values via a value-mapping table. Service type, priority, and resolution notes map to custom fields on the Deal.

Urban Hawks AR session metadata (session_duration, device_type, resolution, issue_resolved flag) migrates as a custom field group on the associated Zoho Deal and as a Task record with the original session timestamp. The AR session type (remote_assist, on_site_annotate) maps to Task Type values in Zoho.

Urban Hawks customer accounts (company name, address, industry, primary_contact) map 1:1 to Zoho CRM Accounts. Industry pick-list values map via a value-mapping table since Urban Hawks and Zoho may use different industry taxonomy. Parent-account hierarchies are preserved via Zoho's Parent_Account lookup.

Urban Hawks contact records (first_name, last_name, email, phone, job_title) map 1:1 to Zoho CRM Contacts. All standard contact fields transfer directly. Primary contact designation in Urban Hawks migrates as a custom checkbox field (Primary_Contact__c) on the Zoho Contact. The contact's Zoho CRM ID is linked to the original Urban Hawks contact identifier for cross-reference reporting.

Urban Hawks field notes attached to work orders map to Zoho CRM Notes. Original note timestamps and creator (technician) name are preserved. Rich-text formatting in Urban Hawks notes is converted to plain text for Zoho Note compatibility. Any embedded images within notes are exported as file attachments linked to the parent Deal.

Urban Hawks file attachments (AR session screenshots, annotated images, PDF field reports) re-upload to Zoho CRM as Attachments on the corresponding Deal record. File size limits apply: Zoho CRM default 25MB per file; larger AR images are resized or split before import.

Urban Hawks custom properties on work orders (service_category, travel_distance, parts_used, customer_signoff) that have no direct Zoho CRM equivalent become custom fields on the Deal module. We create the custom field in Zoho before migration, then map values during the import phase.

Urban Hawks technician assignment logs (who was assigned, when, for which work order) map to Zoho Task history linked to the Deal. This preserves a chronological technician-assignment record in Zoho without requiring a custom junction object. Each assignment task records the technician's Zoho User ID, assignment date, and the associated Deal ID for audit trail completeness.

Urban Hawks customer sign-off records (digital signature, service completion approval) have no native Zoho CRM equivalent. We preserve these as PDF attachments on the Deal record and surface them in the migration report for manual re-creation in Zoho's native e-signature integration if required.