Migrate from Urban-Hawks to Twenty CRM

Urban Hawks contacts (customers, site managers, dispatch contacts) map directly to Twenty People. Each Person record requires a unique identifier — we match on email address. If a contact has no email, we generate a deterministic placeholder to prevent duplicates. Company linkage on the Person record (companyId) requires the Company to exist first, so Companies migrate before People.

Urban Hawks companies and service locations map to Twenty Companies. We preserve the full address (street, city, state/province, postal code, country) in Twenty's address fields. Service locations with a parent company link map to Companies with a Parent CompanyId. Multi-location organizations may produce multiple Company records per customer — we surface this for your team to deduplicate post-migration.

Urban Hawks technician records become Twenty Workspace Member invitations. Owner resolution matches technician email addresses to existing Twenty users; unmatched technicians receive an invitation to join the Twenty workspace before migration runs. All work order and asset records assigned to a technician get their Twenty userId linked via OwnerId or a custom Assigned_To__c field.

Open Urban Hawks work orders map to Twenty Opportunities. Work order status (Pending, In Progress, Completed, Cancelled) maps to Opportunity Stage values — we create a custom stage set in Twenty matching Urban Hawks' status taxonomy. Closed-won maps to a Completed stage; cancelled maps to Closed Lost. The Opportunity name defaults to Work Order number + customer name for traceability.

If your team needs to preserve work-order-specific fields that don't fit Opportunity semantics (e.g., asset serial numbers, service type, priority level, scheduled date), we create a custom Jobs object in Twenty. Jobs links to the Opportunity and to the asset Company via relation fields. This requires your Twenty admin to enable custom object creation in workspace settings before migration.

Urban Hawks assets and equipment records map to a custom Assets object in Twenty if you need to track them separately from Companies. The Assets object links to the associated Company (service location) via a relation field. If assets are primarily identified by their location, they may instead become Company custom fields — we surface this choice in the migration plan.

Urban Hawks work order notes, status changes, and technician check-ins map to Twenty Tasks. Each activity creates a Task record linked to the parent Opportunity or Jobs record. Original timestamps and technician names are preserved in Task fields. High-volume activity logs may exceed Twenty's 20,000-record CSV import limit — we batch these via API.

Urban Hawks files attached to work orders, assets, or contacts are downloaded and re-uploaded to Twenty's storage. Files attach to the target record (Opportunity, People, or custom Assets object) using Twenty's file attachment model. Large files or bulk attachments are migrated via API in batches to avoid timeout errors.

Any Urban Hawks custom fields not covered by standard mappings become Twenty custom fields on the appropriate object. Twenty supports text, number, date, select, multi-select, relation, and other field types. We match field types during mapping: Urban Hawks dropdowns become Twenty select fields with the same options preserved via value mapping.

Urban Hawks field service workflows (dispatch rules, routing logic, technician assignment triggers) do not have a direct equivalent in Twenty CRM. We export your workflow definitions as a structured JSON reference document that your Twenty admin can use to rebuild equivalent automations in Twenty's workflow builder. The rebuild is manual because automation logic is destination-specific.