Migrate from Urban-Hawks to Freshsales

Direct 1:1 map for most contact records. Freshsales Contact requires an AccountId — contacts without a primary company in urban-hawks attach to a default placeholder Account or are linked to the first associated company found. Email uniqueness checks run against Freshsales Contact records before insert.

Records with urban-hawks lifecycle_stage values indicating early funnel (Subscriber, Lead, Marketing Qualified) route to Freshsales Lead. Records at Customer or Evangelist stage route to Freshsales Contact. The split rule is configurable — some teams prefer all records to land as Contacts and use Lead conversion after go-live.

Direct map. Urban-hawks company hierarchies (parent/child) map to Freshsales Account Parent Account field. Multi-company associations on a single urban-hawks contact collapse to a primary AccountId in Freshsales; additional associations are created as Account Contact Relationships. If your workflows reference specific company-to-contact links, those relationships are recreated in Freshsales using the Account Contact Relationship object. Parent companies must be migrated before child companies to respect the Parent Account dependency.

Direct map. Each urban-hawks deal pipeline maps to a Freshsales pipeline. Stage values are mapped pick-list to pick-list per pipeline. Freshsales Opportunity requires an AccountId — deals without a linked company use the primary AccountId from the deal's primary contact.

Urban-hawks pipeline definitions become Freshsales pipeline definitions. Each pipeline requires its own Stage configuration in Freshsales — stage names, probabilities, and forecast categories are set per pipeline. We deliver the mapping plan so your admin can pre-create pipelines before data loads.

Stage names mapped value-by-value per pipeline. Urban-hawks stage probability percentages map to Freshsales Stage Probability field. If Freshsales lacks a matching stage name, we create it as part of the pipeline setup plan or flag it for admin decision before migration.

Freshsales has no native lifecycle_stage equivalent, so the property migrates as a custom pick-list field (Lifecycle_Stage__c) on both Contact and Lead objects. Stage-changed timestamps migrate as a separate custom datetime field (Lifecycle_Stage_Changed__c) for reporting continuity. If your team relies on stage transition history for analytics, the custom datetime field preserves the timing of each stage change recorded in urban-hawks.

Support tickets map to Freshsales Cases. Ticket status (Open, Pending, Resolved, Closed) maps to Freshsales Case Status values. Priority maps to a custom pick-list field or uses Freshsales native Priority if the value set matches. Owner resolved by email match to Freshsales users.

Product catalog items map 1:1 to Freshsales Products. Name, description, price, cost, and unit map directly. Products must exist before line items that reference them — product migration runs before line item migration. SKU lookups are preserved to support line item product reference validation. If a product has associated attachments or images, those are flagged for manual reattachment after migration.

Deal line items map to Freshsales Opportunity Line Items. Each line item references a Product by name or SKU lookup. Quantity, unit price, and discount transfer directly. Line items without a matching product are flagged for admin resolution before the full run.

Urban-hawks custom objects migrate to Freshsales Custom Modules on Enterprise ($59/user/mo) or to custom fields on standard objects for Pro/Growth plans. Custom object relationships (N:N) require Freshsales Custom Module associations to be configured first — we deliver a schema setup plan before data moves. If your custom objects have lookup fields to other objects, those lookups must reference Freshsales record IDs, which are only available after the target objects have migrated.

Files attached to contacts, companies, deals, or tickets are downloaded from urban-hawks and re-uploaded to Freshsales as File Attachments. File size limits apply (Freshsales Growth plan includes 2GB per user; Enterprise includes 100GB per user). We flag oversized files before migration so you can decide whether to trim or provision additional storage.