Migrate from Pawa to HubSpot

Pawa contact records map directly to HubSpot Contacts. Email address serves as the primary identifier for deduplication. Pawa's custom contact properties migrate to HubSpot custom contact properties with type-aware mapping (text, number, date, picklist). We also map phone fields, preserving original formats, and preserve the original Pawa record ID as a custom property for future delta imports.

Pawa stores lifecycle or status indicators in custom properties. HubSpot has a built-in lifecycle_stage property for marketing-sourced contacts. We populate HubSpot's lifecycle_stage with the Pawa equivalent value and preserve the original Pawa field name as Source_Status__c for audit continuity and traceability.

Pawa company records map to HubSpot Companies. Company name, domain, industry, employee count, and annual revenue map to HubSpot standard properties. HubSpot's industry pick-list values require value-by-value mapping against Pawa's industry taxonomy. We also map address fields, phone numbers, and any custom company properties, applying the same type-aware mapping used for contacts.

Pawa parent-child company relationships map to HubSpot's Parent Company field on the child Company record. Circular reference detection runs before migration to prevent infinite loops in the company hierarchy. If a circular hierarchy exists, we resolve it by collapsing the loop into a flat parent-child structure, preserving the most recent relationship based on modification timestamps, and log a warning for manual review.

Pawa deals migrate to HubSpot Deals. Deal name, amount, close date, and owner map directly. HubSpot's dealstage property maps to HubSpot Pipeline Stage by resolving the target pipeline ID from your HubSpot account configuration. We also map custom deal fields, preserve the original Pawa deal ID, and handle currency conversion if the deal amounts are stored in a non-USD currency, using exchange rates from the migration date.

Pawa pipeline definitions map to HubSpot Pipelines. Each Pawa pipeline becomes a HubSpot Pipeline. Pawa stage names map to HubSpot Stage names by value; stage probability values are applied as HubSpot's stage probability field if the Pawa data includes probability metadata.

Pawa Enterprise custom objects map 1:1 to HubSpot Custom Objects (requires Enterprise tier). We create the HubSpot custom object schema based on the Pawa custom_object_type API response, including field types, required flags, and relationship fields. If Pawa's custom object includes linked records, we map those relationships using HubSpot's association API and configure any junction objects required for many-to-many cardinality, ensuring referential integrity after migration.

Pawa N:N relationships between custom objects map to HubSpot custom object association properties. The Pawa relationship record schema determines whether the HubSpot association is a many-to-many (requires junction object) or one-to-many (direct lookup). During migration, we inspect each relationship record's foreign key fields and create the appropriate HubSpot association properties, flagging any ambiguous cases for manual review before committing to the schema.

Pawa call records exposed via the engagement API map to HubSpot Call Engagements on the associated Contact timeline. Original call timestamp, duration, outcome, and owner are preserved as HubSpot call metadata properties. We also map any custom call fields (e.g., call type, disposition) to HubSpot's custom call properties, and if the call was logged in a non-English language, we preserve the original language tag for compliance.

Pawa email engagement records map to HubSpot Email Engagements. Subject line, body content, sent timestamp, and recipient association migrate to the HubSpot contact timeline via the Engagements v3 API. We preserve HTML formatting where present, strip any Pawa-specific tags, and attach any embedded images as HubSpot file references, ensuring the email body renders correctly in HubSpot's timeline.

Pawa meeting records become HubSpot Meeting Engagements. Start time, end time, title, body, and associated contacts map to HubSpot's meeting engagement properties with original timestamps preserved. We also map the meeting location (if stored), any meeting notes, and the meeting organizer, attaching these as additional properties to the HubSpot meeting engagement, while preserving the original Pawa meeting ID for traceability.

Pawa note records migrate as HubSpot Note Engagements attached to the relevant Contact or Company. Rich-text formatting is preserved where the source data includes HTML; plain-text notes map without transformation. We also preserve any @mention tags used in Pawa notes, converting them to HubSpot contact or company mention links if the referenced record exists in HubSpot, otherwise retaining the original text.

Pawa user records resolve to HubSpot Owners by email match. Unmatched Pawa users are flagged in the pre-migration validation report with a fallback owner assignment option before the migration run commits. If no fallback is chosen, we assign the records to a designated system owner in HubSpot, ensuring no data is left without an owner after migration, and we log each assignment for audit purposes.

Pawa file attachments on contacts, companies, or deals are downloaded and re-uploaded to HubSpot Files. File associations are recreated as HubSpot file-to-record links. Size limits reflect HubSpot's attachment constraints. We verify each file's MIME type and preserve original filenames, mapping them to HubSpot's file naming convention. For files exceeding HubSpot's 25MB limit, we flag them for manual handling and provide a detailed report listing the oversized assets.