Migrate from Urban-Hawks to Pipedrive

Urban Hawks Person maps directly to Pipedrive Person. Pipedrive requires an org_id to link a Person to an Organization — if Urban Hawks Person has no primary company, the Person migrates with org_id = null and is flagged for manual assignment in Pipedrive.

Urban Hawks Organization maps 1:1 to Pipedrive Organization. Pipedrive uses structured address fields (address, zip, city, state, country) — address components from Urban Hawks are mapped to the corresponding Organization address fields. If Urban Hawks stores address components in separate fields, each component is mapped to its corresponding Pipedrive Organization address field. This ensures address data is fully searchable and displayable in Pipedrive's interface.

Urban Hawks Deal maps to Pipedrive Deal. Pipedrive Deal uses stage_id linked to a Pipeline; stage values from Urban Hawks are mapped to the correct stage within the target Pipedrive pipeline, preserving order and probability. FlitStack validates stage mapping by comparing source stage labels against Pipedrive stage names, ensuring deals land in the correct pipeline stages after migration.

Urban Hawks call activity migrates as Pipedrive Activity with type = 'call'. Subject, duration (in minutes), result, and done flag are mapped directly. Owner is resolved by email match to Pipedrive user. Call outcome details from Urban Hawks are preserved in the result field, and the activity timestamp is set to match the original call date and time in Pipedrive.

Urban Hawks meeting activity migrates as Pipedrive Activity with type = 'meeting'. Subject, start time, end time, location, and done flag map directly. Original meeting owner is resolved by email to Pipedrive user. Meeting description and attendee information from Urban Hawks are preserved in the activity notes field, maintaining full context of each meeting.

Urban Hawks email activity migrates as Pipedrive Activity with type = 'email'. Subject, body content, and link to the parent Person or Deal are preserved. Pipedrive email tracking depends on the email sync integration — activity text is migrated regardless.

Urban Hawks notes migrate as Pipedrive Notes. Content maps to the Note body field; the parent Person, Organization, or Deal is preserved via Pipedrive's polymorphic content_object reference. Note creation timestamps are migrated as Pipedrive note timestamps. If Urban Hawks notes include HTML formatting, FlitStack strips unsupported tags while preserving plain text content for clean display in Pipedrive.

Urban Hawks product catalog maps 1:1 to Pipedrive Products. Product name, code, unit price, and description are transferred. Products are imported before Deals so deal_product associations can link correctly. Product images and attachments from Urban Hawks are downloaded and re-uploaded to Pipedrive Products, maintaining visual reference for sales teams.

Urban Hawks custom fields on Person cannot be mapped by ID to Pipedrive because Pipedrive generates new hash keys for each custom field. FlitStack creates the Pipedrive custom field via POST /personFields with matching name and field type before migration, storing the Urban Hawks field ID for traceability.

Urban Hawks deal custom fields are recreated in Pipedrive via POST /dealFields before migration runs. Leads in Pipedrive inherit deal custom fields automatically per Pipedrive's shared-field model. Each custom field gets a Pipedrive hash key assigned at creation time. The mapping between Urban Hawks field IDs and Pipedrive hash keys is stored in the migration manifest for traceability.

Pipedrive multi-select fields require the field to be created first via API, then each option value is mapped individually in the import step. Urban Hawks multi-select values are mapped one-by-one to the corresponding Pipedrive option labels. If an option label doesn't exist in Pipedrive, FlitStack creates it automatically before writing values, ensuring no data is lost during migration.

Urban Hawks line-item or product-association data on a Deal transforms into Pipedrive's deal_product association object. Each linked product carries product_id, quantity, discount_percent, and item_price into the association table. FlitStack validates that each product_id exists in Pipedrive before creating the association; if a product is missing, it is created on-the-fly to prevent null references.

Urban Hawks owner_id does not map directly to Pipedrive user_id. FlitStack resolves owners by matching the owner's email address from Urban Hawks against the /users endpoint in Pipedrive. Unmatched owners are flagged and assigned to a fallback Pipedrive user pending team review.

File attachments from Urban Hawks are downloaded and re-uploaded to Pipedrive Files, linked to the parent Person, Organization, or Deal record. Pipedrive file size limits apply — files over the plan limit are flagged for manual handling. File metadata including creation date and uploader information is preserved in Pipedrive's file description field for audit purposes.