Migrate from Patent Hive to Mailchimp

Inventor contact records map 1:1 to Mailchimp subscriber profiles. The email address serves as the primary subscriber identifier, acting as the unique key for each inventor in Mailchimp. First name, last name, phone number, and company organization map to standard Mailchimp merge fields (FNAME, LNAME, PHONE, COMPANY), preserving all standard contact information in native Mailchimp fields.

Patent application records have no direct Mailchimp equivalent, as Mailchimp is not designed for patent portfolio management. Each application links to its inventor in Patent Hive. We denormalize application metadata onto the inventor's Mailchimp profile as custom merge fields: application number, filing date, jurisdiction code, and current status value. This denormalization preserves all patent-specific data while adapting it to Mailchimp's subscriber schema.

Patent Hive application-stage values (Filed, Under Review, Granted, Abandoned, Rejected) map to Mailchimp tags on the inventor subscriber profile. Multiple tags per inventor support cases where one inventor has multiple applications in different stages. This tag-based approach enables segmentation and campaign routing based on application status across the inventor's patent portfolio.

Assignee organization from Patent Hive maps to the standard Mailchimp COMPANY merge field, preserving organizational affiliation. For multi-client IP firms, the organization also generates a per-client tag on the subscriber so campaigns can target inventors by client. This dual approach maintains both the contact's company information and enables client-based segmentation for IP firms managing multiple portfolios.

Patent Hive office actions, filing receipts, and correspondence PDFs re-upload as Mailchimp file attachments on the inventor profile where file sizes permit. Links to large documents exceeding Mailchimp's 30MB limit store in a custom merge field pointing to the re-hosted URL, since Mailchimp file size constraints apply to direct attachments. This approach preserves document access while respecting Mailchimp's platform limitations.

Examiner notes and office action summaries from Patent Hive migrate as Mailchimp notes attached to the subscriber profile. These are human-readable context fields that preserve examiner communication history, not structured data, so they attach as free-text notes rather than merge fields. This approach keeps the narrative context accessible within each inventor's subscriber profile.

Jurisdiction codes from Patent Hive (US, EP, WO, CN, etc.) map to a custom merge field (JURISDICTION) for structured data storage. Optionally, jurisdiction codes also generate per-jurisdiction tags for segmented campaigns targeting inventors by geographic patent coverage. Value mapping ensures standardized codes land correctly in Mailchimp without character or format issues.

Filing dates and priority dates from Patent Hive migrate as custom date-type merge fields in Mailchimp, preserving temporal patent data. These date fields support date-based segmentation for anniversary-triggered campaigns, deadline-notification automations, and time-sensitive IP communications based on filing milestones.

The source-system internal ID from Patent Hive stores as a custom merge field (SOURCE_PATENT_ID) on each subscriber for traceability and audit purposes. This field enables delta-run de-duplication across migration iterations, ensuring that subsequent migration runs can accurately match Mailchimp subscribers back to their original Patent Hive records.

Patent Hive filing-deadline and examiner-response workflows have no Mailchimp equivalent due to fundamental differences in event models and trigger architectures. These must be rebuilt in Mailchimp's automation builder post-migration using the migrated application data (filing dates, next-action dates, status tags) as trigger conditions for deadline notifications and status-change alerts.

Co-inventor relationships in Patent Hive split into individual subscriber profiles in Mailchimp, with each inventor receiving their own separate profile. A collaborator tag and a subscriber note listing co-inventor names preserves the relationship context without replicating Patent Hive's multi-parent link model. This approach maintains relationship data while conforming to Mailchimp's single-profile-per-contact architecture.

Communication preferences and opt-in flags from Patent Hive map to Mailchimp interest groups or tags depending on preference type. Value mapping ensures specific preference values route to the correct Mailchimp interest setting on the subscriber profile, enabling preference-based segmentation and respecting inventor communication preferences across email campaigns.