CRM migration

Migrate from Patent Hive to Nutshell

Field-level mapping, validation, and rollback between Patent Hive and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.

Patent Hive logo

Patent Hive

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

12 of 12

objects map 1:1 between Patent Hive and Nutshell.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Patent Hive logo

Patent Hive

What's pushing teams away

  • Limited to UAE residents and registered entities—international inventors and multinational corporations face jurisdictional constraints not present in global patent filing systems.
  • New initiative with no track record: launched January 2025 with unproven long-term stability, unlike established patent systems with decades of precedent.
  • No documented API or developer ecosystem, preventing integration with existing IP management workflows or automated portfolio tracking systems.

Choosing

Nutshell logo

Nutshell

What's pulling them in

  • Lowest cost entry point among mid-market CRMs—Foundation plan starts at $13/user/month, making it accessible for teams validating CRM fit before committing.
  • Integrated sales automation and email sequencing on Pro plans without requiring a separate email marketing platform, per verified Capterra reviews.
  • Consistently praised for intuitive interface and fast onboarding, with case studies reporting 100% team adoption rates within initial deployment periods.
  • Strong customer support responsiveness cited across G2 reviews, with dedicated support tiers available on Enterprise plans.
  • Native integrations with WhatsApp, Facebook Messenger, Instagram, and Slack reduce reliance on third-party middleware for common communication channels.

Object mapping

How Patent Hive objects map to Nutshell

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

maps to

Nutshell

Company

1:1
Fully supported

Each 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

maps to

Nutshell

Person

1:1
Fully supported

Inventors 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

maps to

Nutshell

Company

1:1
Fully supported

Corporate 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

maps to

Nutshell

Deal (Pipeline Stage)

1:1
Fully supported

Patent 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)

maps to

Nutshell

Custom Field on Company

1:1
Fully supported

Patent 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)

maps to

Nutshell

Custom Field on Company

1:1
Fully supported

Numeric 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)

maps to

Nutshell

Note on Company

1:1
Fully supported

Patent 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

maps to

Nutshell

Activity (Task)

1:1
Fully supported

Office 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

maps to

Nutshell

Custom Field on Company

1:1
Fully supported

Priority 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

maps to

Nutshell

Custom Field on Deal

1:1
Fully supported

When 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

maps to

Nutshell

Custom Field on Company

1:1
Fully supported

Patent 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

maps to

Nutshell

User

1:1
Fully supported

Patent 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.

Gotchas + challenges

What specifically takes care here

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 logo

Patent Hive gotchas

High

Patent Hive is a government program, not software

Medium

Hive project management confusion

High

No public API documentation discovered

Nutshell logo

Nutshell gotchas

High

Contact tier limits enforced on import

Medium

No bulk API endpoint requires paginated extraction

Medium

Email sequences not exportable via API

Medium

Foundation plan disables key sales features

Pair-specific challenges

  • Patent Hive has no native deal or pipeline object — every prosecution stage must map to a Nutshell custom field or pipeline stage

    Patent Hive tracks prosecution status through custom fields or internal attributes, not a deal pipeline. Nutshell's Deal object with pipeline stages is the closest construct, but it is designed for sales workflows. We create a dedicated patent pipeline in Nutshell with stages matching prosecution states (Filed, Examination, Published, Granted, Abandoned) and preserve stage-entry timestamps as custom datetime fields. Stage transitions that occurred in Patent Hive cannot be automatically replayed in Nutshell's pipeline because Nutshell tracks current stage only, not stage history.

  • Patent Hive's multiple-value custom fields collapse to multiple entries in Nutshell's custom field model

    Patent Hive allows multiple values per custom field (e.g., a patent can have multiple technology classifications). Nutshell's custom fields on Company are single-value by default. We handle this by either storing multiple values as a delimited text string in a custom field, creating multiple custom fields per value, or linking to a secondary custom object for multi-value tracking. The approach is chosen during the sample migration phase and documented in the mapping plan before full migration runs.

  • Nutshell's reporting limitations mean IP analytics require post-migration export to BI tools

    Nutshell's native reporting is described as limited by users, with detailed analysis requiring Excel exports. Patent Hive's built-in IP analytics (portfolio valuation, prosecution trends, technology coverage maps) have no equivalent in Nutshell. We migrate all underlying data completely so that reporting rebuilds in Nutshell or a connected BI tool capture the full history. Custom fields used for IP classification are preserved exactly as configured in Patent Hive so that portfolio-level filtering remains possible.

  • Inventor-to-patent relationships require junction handling when an inventor is associated with multiple patents

    Patent Hive supports N:N relationships between inventors and patents natively. Nutshell Person records link to Companies, but a single Person may represent an inventor across multiple patent Companies. We map each Person-Company pair explicitly, creating multiple relationships where they exist. If Nutshell's Person-Company link does not support relationship metadata (e.g., inventor type: primary vs secondary), we store this in a custom field on the Person record. We check for duplicate Person records that may arise from variations in inventor name formatting, applying normalization before linking. Relationship metadata, such as primary vs secondary inventor, is stored as a picklist field on the Person record, preserving classification in Nutshell without junction objects.

  • Original create dates and modification timestamps require custom datetime fields since Nutshell sets CreatedDate at import time

    Nutshell's system timestamps (CreatedDate, LastModifiedDate) reflect the migration import, not the original Patent Hive record creation. For IP portfolios where record age and prosecution timeline matter for maintenance deadlines and bar-date calculations, we preserve the original filing date, priority date, and any stage-transition timestamps as custom datetime fields on the Company record. This ensures that anniversary calculations and deadline tracking work correctly post-migration. We also map the original submission date and any patent office action dates as separate datetime fields to support docketing and renewal workflows. If the source data includes historical stage-transition events, these are logged as activity entries on the Deal record, providing a timeline view within Nutshell.

Migration approach

Six steps for a successful Patent Hive to Nutshell data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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

Context on both ends of the pair

Patent Hive logo

Patent Hive

Source

Strengths

  • Aims to reduce UAE patent registration from 42 months to 6 months through expedited processing
  • Includes reduced and zero-cost filing tiers for students and young inventors under 21
  • Backed by the UAE Ministry of Economy with strategic alignment to national innovation goals
  • Green IP Roadmap integration offers 3-6 month expedited track for environmental sustainability patents

Weaknesses

  • No documented API, data export capability, or developer interface for integration or migration
  • Operated by a government ministry; operational continuity depends on government policy and budget
  • Limited scope to UAE jurisdiction; international patent filings require separate PCT or national phase entries
  • New initiative launched January 2025 with no published long-term pricing or service level commitments
Nutshell logo

Nutshell

Destination

Strengths

  • Simple, intuitive interface with minimal learning curve for sales teams new to CRM
  • Per-seat pricing is transparent and predictable, with annual billing reducing monthly cost
  • Full data export tool available for all account data including backups
  • Open JSON-RPC API allows programmatic access to all core objects
  • Native multichannel engagement (email, SMS, WhatsApp) without third-party add-ons for communication

Weaknesses

  • Reporting and analytics are considered weak, requiring manual Excel exports for detailed analysis
  • No bulk API endpoint—migration requires paginated API reads that must be rate-limited carefully
  • JSON-RPC API is less common than REST, requiring custom integration code compared to standard REST CRMs
  • Add-on costs (Forms, Nutshell IQ, Email Marketing) are per-company charges that stack on top of per-seat pricing
  • Feature restrictions on entry-level plans mean teams often need mid-tier to get basic automation

Complexity grading

How hard is this migration?

Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Patent Hive and Nutshell.

  • Object compatibility

    B

    1 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Patent Hive: Not applicable — no public API surface exists..

  • Data volume sensitivity

    B

    Patent Hive doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Patent Hive to Nutshell migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Patent Hive to Nutshell data migrations

Answers to the questions buyers ask most during Patent Hive to Nutshell migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Most Patent Hive to Nutshell migrations complete in 48–72 hours for datasets under 25,000 records. The longest phase is schema setup — creating custom fields on Nutshell Companies and Persons to match Patent Hive's field types. Large IP portfolios with hundreds of custom field configurations or multiple-value fields extend to 5–7 days. The sample migration phase typically runs within 24 hours of project kickoff.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Patent Hive.
Land in Nutshell, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day