Migrate from Patent Hive to Salesforce Sales Cloud

Patent Hive inventor records map directly to Salesforce Contacts. Each inventor's name, email, address, and contact details translate to the standard Contact fields (FirstName, LastName, Email, Phone, MailingAddress). Inventor IDs are preserved as Source_System_ID__c for delta-run de-duplication. If Patent Hive stores inventor organization affiliation, that maps to AccountId via the existing Company/Account mapping.

Patent Hive company records — typically the patent holder or assignee organization — map to Salesforce Accounts. Company name, industry, address, and employee count translate directly. Parent-company hierarchies in Patent Hive map to Account.ParentId. Multi-company affiliations per patent require junction object handling.

Patent Hive patent records have no Salesforce standard object equivalent. We create a Patent__c custom object with fields for title (Name), patent number (Patent_Number__c), filing date (Filing_Date__c), grant date (Grant_Date__c), jurisdiction (Jurisdiction__c), status (Patent_Status__c), and renewal date (Renewal_Date__c). The custom object is created in your Salesforce org before migration; we deliver the setup plan as part of the engagement.

Patent Hive application records — representing patent applications in process — map to Salesforce Opportunities using a Record Type specific to IP pipelines. Application name becomes Opportunity.Name, filing fee maps to Amount, application date maps to CloseDate, and application status maps to StageName via value-mapping. Each jurisdiction's application stages map to Opportunity Stage values.

Patent Hive's inventor-to-patent relationship with role and ownership percentage has no Salesforce standard equivalent. We create Inventor_Patent__c as a junction object with lookup fields to Contact (Inventor__c) and Patent__c (Patent__c), plus fields for Role (Role__c) and Ownership_Percentage__c. Multi-inventor patents generate one junction record per inventor.

Patent Hive filing history entries — Office Actions, Responses, Amendments — map to Salesforce Tasks with Type='IP Filing Event'. Original filing event timestamps, assigned examiners, and action descriptions preserve as Task fields. High-priority deadlines map to Salesforce Events with reminders.

Patent Hive PDF attachments (patent documents, drawings, correspondence) re-upload to Salesforce Files via ContentVersion. Each file is linked to the corresponding Patent__c record via ContentDocumentLink. Salesforce's 25MB per-file limit applies; oversized files are flagged for pre-migration splitting and returned to you with recommendations for external PDF division before the migration run.

Patent Hive renewal and maintenance records map to Salesforce Tasks with Type='Renewal' or 'Maintenance'. Due dates map to ActivityDate, and renewal cost maps to a custom currency field. Recurring renewal tasks can be scheduled in Salesforce after migration. We recommend configuring Salesforce reminder notifications for each task to replace Patent Hive's automatic alerts.

Patent Hive jurisdiction values (USPTO, EPO, WIPO, CNIPA, etc.) map to a Jurisdiction__c custom picklist on Patent__c. Value-by-value mapping applies for all jurisdictions present in the source data. New jurisdictions discovered during migration are flagged for review and added to the picklist definition for validation before the full migration run.

Patent Hive owner and assigned attorney records resolve to Salesforce Users by email match. Unmatched owners are flagged before migration — your team either creates the Salesforce user or assigns records to a fallback owner. Owner change history preserves as a custom audit field.

Patent Hive workflows (deadline alerts, renewal reminders, status-change triggers) have no Salesforce equivalent and do not migrate. We export workflow definitions as a structured JSON reference document for your Salesforce admin to rebuild in Flow. Deadline-based flows are the highest priority for rebuild.