CRM migration
Field-level mapping, validation, and rollback between Patent Hive and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Patent Hive
Source
Nutshell
Destination
Compatibility
12 of 12
objects map 1:1 between Patent Hive and Nutshell.
Complexity
BStandard
Timeline
48–72 hours
Overview
Patent Hive serves IP management workflows with custom field types (text, numeric, notes) scoped to patent families. Nutshell uses a conventional CRM model built around Companies, People/Contacts, Leads, Deals with customizable pipelines, and Activities. This structural mismatch is the central challenge: Nutshell has no native patent record object, so every Patent Hive field that tracked prosecution status, jurisdiction, or internal classification needs a Nutshell custom field. We handle the data migration — records, relationships, custom fields, and activity history — and surface what must be rebuilt manually: Nutshell's workflow automation, email sequences, and reporting dashboards have no equivalent in Patent Hive's model. The migration uses Nutshell's JSON-RPC API with bulk operations where available, preserving original create dates as custom datetime fields since Nutshell's system timestamps are set at import time. Because Patent Hive stores prosecution stages, jurisdiction codes, and internal classifications as distinct custom field types, each must be recreated in Nutshell with matching data types. Multi-value fields, such as multiple inventors or technology classifications, are transformed into either delimited strings or separate custom fields to preserve the original granularity. All relationships between inventors, assignees, and patent records are converted to Nutshell's Company–Person links, with ownership and assignment metadata stored in custom fields. The migration script runs in batches using the JSON-RPC API's bulk endpoints, and it logs every transformed record to allow audit and rollback if needed.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Patent Hive object lands in Nutshell, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Patent Hive
Patent Record / Patent Family
Nutshell
Company
1:1Each patent record becomes a Nutshell Company. The patent title or application number maps to Company Name. Jurisdiction and filing status stored as custom fields on the Company record. Additional metadata such as filing date, priority date, and internal classification are also migrated as custom fields, preserving the complete prosecution history within the Company record. This approach maintains data integrity and supports future reporting on portfolio performance.
Patent Hive
Inventor
Nutshell
Person
1:1Inventors map to Nutshell Person records. Full name splits into First Name and Last Name. Contact information (email, phone) maps to standard Person fields. Multiple inventors per patent become separate Person records linked to the same Company. If an inventor has multiple email addresses, we preserve the primary address and store alternatives as custom fields. Inventor type (primary, secondary) is captured in a picklist on the Person record.
Patent Hive
Assignee / Patent Owner
Nutshell
Company
1:1Corporate assignees map to Nutshell Companies. When the assignee differs from the inventor company, both entities exist separately and are linked via Nutshell's Company relationship features. We also capture the assignment date and any relevant legal documentation references as custom fields on the Assignee Company record. This ensures that ownership history is preserved and can be reported on in Nutshell's dashboards.
Patent Hive
Prosecution Stage
Nutshell
Deal (Pipeline Stage)
1:1Patent Hive prosecution stages (filed, examination, published, granted, lapsed) map to Nutshell Deal pipeline stages. Each stage requires a corresponding Nutshell pipeline stage value, and stage-entry timestamps are preserved as custom datetime fields. If the source includes stage-transition reasons or notes, these are stored as custom text fields on the Deal, providing context for each status change. The mapping also supports stage colors and labels to align with branding.
Patent Hive
Custom Field (Text)
Nutshell
Custom Field on Company
1:1Patent Hive text custom fields (technology classification, responsible attorney, business unit) migrate as Nutshell text custom fields on the Company object. Single-value vs multiple-value handling determined by source field configuration. For fields marked as multiple-value, we either concatenate values into a delimited string or create a separate custom field per value, depending on the desired reporting granularity. This ensures that all information is preserved without loss.
Patent Hive
Custom Field (Numeric)
Nutshell
Custom Field on Company
1:1Numeric custom fields (internal scores, licensing revenue, prosecution costs) migrate as Nutshell numeric custom fields. Decimal precision preserved where supported by Nutshell's field definition. When Patent Hive stores numeric values in scientific notation or with specific rounding rules, we apply conversion logic to match Nutshell's handling. Any currency fields are migrated as numeric with appropriate decimal places, and unit annotations are kept as a separate text field.
Patent Hive
Custom Field (Notes)
Nutshell
Note on Company
1:1Patent Hive notes fields migrate as Nutshell Notes attached to the corresponding Company record. Notes are visible to all users in the Nutshell account by default. If a note contains references to other patents, inventors, or external documents, we preserve those links as text URLs or file paths. For lengthy notes, we ensure that the content is transferred without truncation, and any formatting is retained as plain text where possible.
Patent Hive
Office Action / Correspondence
Nutshell
Activity (Task)
1:1Office actions and prosecution correspondence migrate as Nutshell Tasks with Type='Call' or a task category. Original dates preserved and linked to the Company record representing the patent. Each task includes the correspondence text as the description, allowing support staff to review context without switching tools. If the correspondence includes attachments, we store the file names and URLs in text fields, and link to a document repository when available.
Patent Hive
Priority Claim
Nutshell
Custom Field on Company
1:1Priority claim data (application number, filing date, jurisdiction) stored as text custom fields on the Company record representing the priority patent. We also capture the priority country code and any PCT or regional filing references as separate text fields, ensuring that the full priority chain is visible in Nutshell for Paris Convention deadline calculations.
Patent Hive
Licensing Revenue
Nutshell
Custom Field on Deal
1:1When patent licensing generates deals, revenue figures stored as custom currency fields on Nutshell Deals. If no deal record exists, revenue stored on the Company as a numeric custom field. We also map recurring royalty payments as separate line items, using a custom numeric field for each period. Any revenue milestones are logged as activity notes, providing a timeline of cash flow events tied to the license agreement.
Patent Hive
External ID / Patent Number
Nutshell
Custom Field on Company
1:1Patent numbers and external system IDs preserved as custom text fields on the Company for traceability. PCT numbers, national phase entries, and publication numbers stored as separate fields or in a multi-value custom field. If the source data includes historical version numbers or superseded IDs, we retain them in a separate text field to preserve audit trails. This approach prevents data loss and supports downstream integration with IP docketing systems.
Patent Hive
User / Attorney
Nutshell
User
1:1Patent Hive users and assigned attorneys mapped to Nutshell Users by email match. Unmatched users flagged for admin assignment before migration commits. We also verify user roles and permissions, aligning them with Nutshell's profile settings to ensure that attorneys retain appropriate access levels post-migration. If a user lacks an email in the source, we create a placeholder account and note it for manual configuration.
| Patent Hive | Nutshell | Compatibility | |
|---|---|---|---|
| Patent Record / Patent Family | Company1:1 | Fully supported | |
| Inventor | Person1:1 | Fully supported | |
| Assignee / Patent Owner | Company1:1 | Fully supported | |
| Prosecution Stage | Deal (Pipeline Stage)1:1 | Fully supported | |
| Custom Field (Text) | Custom Field on Company1:1 | Fully supported | |
| Custom Field (Numeric) | Custom Field on Company1:1 | Fully supported | |
| Custom Field (Notes) | Note on Company1:1 | Fully supported | |
| Office Action / Correspondence | Activity (Task)1:1 | Fully supported | |
| Priority Claim | Custom Field on Company1:1 | Fully supported | |
| Licensing Revenue | Custom Field on Deal1:1 | Fully supported | |
| External ID / Patent Number | Custom Field on Company1:1 | Fully supported | |
| User / Attorney | User1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Patent Hive gotchas
Patent Hive is a government program, not software
Hive project management confusion
No public API documentation discovered
Nutshell gotchas
Contact tier limits enforced on import
No bulk API endpoint requires paginated extraction
Email sequences not exportable via API
Foundation plan disables key sales features
Pair-specific challenges
Migration approach
Extract Patent Hive data via API and profile custom field configurations
We connect to Patent Hive using available API credentials and extract all patent records, inventor profiles, custom field definitions, and activity history. During extraction, we identify which custom fields are text vs numeric vs notes, which are single-value vs multiple-value, and which records contain data in each field. This profile determines the mapping strategy for Nutshell custom fields and informs the scope of the migration plan.
Design Nutshell custom field schema and patent pipeline before data import
Before migrating any records, we create the custom fields on Nutshell's Company and Person objects to host Patent Hive data. A dedicated patent pipeline with prosecution-stage stages is configured in Nutshell. Fields are created via Nutshell's API with the appropriate field types (text, numeric, currency, datetime, picklist) matching Patent Hive's data profile. This ensures the schema exists before records land, preventing import failures from missing field errors.
Resolve inventor and assignee relationships by email match against Nutshell users
Inventors and assignees who are also Nutshell users get matched by email. Unmatched inventors become Person records without Nutshell user accounts. We flag any duplicate Person records that would be created from the same inventor appearing in multiple Patent Hive entries, consolidating them into a single Person with multiple Company relationships. Attorney and internal team users are matched and assigned as Deal owners where applicable.
Run a sample migration of 50–200 patent records with field-level diff
A representative slice of Patent Hive records migrates first — spanning patents across different prosecution stages, inventors with varying relationship counts, and records with populated and empty custom fields. We generate a field-level diff comparing source values against the migrated Nutshell records so you can verify custom field mapping, relationship resolution, and date preservation before the full run commits. Mapping adjustments happen at this stage.
Execute full migration with delta-pickup window and audit log
The full dataset migrates to Nutshell with a delta-pickup window of 24–48 hours capturing any Patent Hive records modified during the cutover. Every operation is logged in an audit trail covering record count, field mapping applied, relationship links created, and any records that failed to migrate with error reasons. One-click rollback is available if reconciliation identifies unexpected discrepancies. Post-migration, we deliver a summary report showing record counts per object, custom field coverage, and any unresolved relationships requiring manual attention.
Platform deep dives
Patent Hive
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Patent Hive and Nutshell.
Object compatibility
1 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Patent Hive: Not applicable — no public API surface exists..
Data volume sensitivity
Patent Hive doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Patent Hive to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Patent Hive to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Patent Hive
Other ways to arrive at Nutshell
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.