Migrate from Patent Hive to HubSpot

Patent Hive's applicant entity maps directly to HubSpot Contact. Applicant name, email, phone, address, and role map to HubSpot's standard contact properties. Multiple applicants per patent filing map via HubSpot's primary-contact association with additional applicants recorded as secondary association labels.

When an applicant is an organization rather than an individual, Patent Hive's company entity maps to HubSpot Company. Company name, jurisdiction, industry, and size properties translate to HubSpot's standard company fields. Parent-subsidiary relationships in Patent Hive map to HubSpot's company hierarchy.

Patent Hive's patent filing entity maps to a HubSpot Deal (Opportunity). Patent title becomes the Deal name, filing date maps to Close Date (using Close Date as the target milestone date), and application number maps to a custom string field. Each filing becomes a single deal record with the applicant contact and company associated.

Patent Hive application status values (Filed, Under Examination, Published, Granted, Abandoned, Rejected) map to HubSpot deal stage values via a value-by-value mapping. Each status maps to a distinct stage in a Patent Pipeline so the filing lifecycle is visible as a Kanban view in HubSpot. Stage-enter timestamps are preserved as custom datetime fields.

HubSpot's Deal Close Date is a required field with business semantics tied to pipeline stages. The original patent filing date is a different concept — it needs its own custom datetime field (Original_Filing_Date__c) to preserve the actual submission date without conflating it with the deal's expected close or milestone date.

Patent Hive tracks application type (Provisional, Non-Provisional, PCT, Utility, Design) and jurisdiction (USPTO, EPO, WIPO, national filings) as separate properties. HubSpot has no native equivalent — these migrate as custom pick-list fields on the Deal. Jurisdiction-specific deadline rules may require workflow-based reminders in HubSpot.

Patent Hive's examiner assignment property maps to a custom field (Examiner_Name__c) on the Deal. If the examiner is a HubSpot user, their contact can be associated as a secondary deal owner via HubSpot's Owner field — otherwise the name is stored as a read-only text custom field.

HubSpot Deal Amount holds a single monetary value. Additional fee fields from Patent Hive — Filing_Fee__c, Examination_Fee__c, Registration_Fee__c — migrate as separate custom number fields on the Deal. The primary Deal Amount can be set to total estimated portfolio value or left blank per your reporting preference.

Office Action dates and correspondence records in Patent Hive map to HubSpot Tasks with a custom type label ('Office Action') and original timestamps preserved. This keeps the filing's correspondence history visible directly on the deal record in HubSpot's activity timeline.

Patent Hive IPC classification codes, priority dates, and publication numbers have no HubSpot native equivalent. Each migrates as a dedicated custom field on the Deal — IPC code as a text or pick-list field, priority date as a datetime field, and publication number as a read-only text field for reference and cross-referencing.

Patent Hive owner or IP administrator names are resolved against HubSpot users by email match. Unmatched owners are flagged before migration — your team either creates HubSpot user accounts for them or assigns records to a fallback owner. No deal lands in HubSpot without an assigned owner.

Patent Hive document attachments (PDFs of filed applications, office actions, certificates) are downloaded and re-uploaded as HubSpot file attachments on the corresponding deal record, preserving original file names and metadata. File size limits apply — HubSpot handles files up to the portal's attachment size cap, and any oversized files are flagged for manual upload.