CRM migration

Migrate from Perfect Portal to Nutshell

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

Perfect Portal logo

Perfect Portal

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

11 of 11

objects map 1:1 between Perfect Portal and Nutshell.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Perfect Portal is a legal practice management and client-portal platform where the primary record is the Matter, with Party records (contacts), Document references, Stage milestones, and Time/Billing entries attached. Nutshell is a standard small-business CRM organized around People, Companies, Leads, and Deals with a visual pipeline. The two platforms share a party-record model but diverge sharply on the deal concept: Perfect Portal's Matters become Nutshell's Deals, and Perfect Portal's Stage milestones map to Nutshell's pipeline stage transitions. We extract Perfect Portal data via API (parties, matters, events, custom fields) and import into Nutshell's People, Companies, Leads, Deals, and Activities. Document files are re-uploaded to Nutshell's attachments. Automation rules, billing configurations, and client-portal settings have no Nutshell equivalent and must be rebuilt post-migration — we export your Perfect Portal rule definitions as a rebuild reference. The migration runs as a sequenced import (companies first, then people, then matters as deals) with a 24–48 hour delta pickup window to capture in-flight changes during cutover.

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

Perfect Portal logo

Perfect Portal

What's pushing teams away

  • Perfect Portal does not appear to offer a public API or bulk data export mechanism, making self-service migration difficult and requiring manual or vendor-assisted extraction.
  • Cloud-based storage of privileged client matter data introduces data residency and confidentiality concerns that some firms find difficult to accept, particularly around third-party access.
  • The portal is a bolt-on product tightly coupled to its host practice management system, limiting flexibility if the firm wants to switch underlying PMS providers.
  • Per-matter pricing for client access can scale unpredictably as the firm grows, with no published tiered discount structure for high-volume practices.

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 Perfect Portal objects map to Nutshell

Each row shows how a Perfect Portal 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.

Perfect Portal

Party

maps to

Nutshell

Person

1:1
Fully supported

Perfect Portal Party records map directly to Nutshell People. The party name, email address, phone number, role on matter, and mailing address all have direct equivalents in Nutshell's Person fields. Party type (e.g., client, opponent, referrer) is preserved as a custom field on the Nutshell Person record.

Perfect Portal

Matter

maps to

Nutshell

Deal

1:1
Fully supported

Perfect Portal Matter records map to Nutshell Deals. The matter name becomes the Deal name, the matter description becomes the Deal description, the matter value (if present) maps to the Deal amount, and the primary party on the matter links to the Deal's associated Person record. Each matter-type in Perfect Portal can optionally map to a separate Nutshell pipeline.

Perfect Portal

Matter Stage

maps to

Nutshell

Deal Stage

1:1
Fully supported

Perfect Portal Stage milestones track matter progress with a name and timestamp. These are mapped to Nutshell Deal stage values: each Perfect Portal stage name maps to a corresponding Nutshell pipeline stage. Stage-entered timestamps are preserved as custom datetime fields on the Nutshell Deal so historical stage history is visible in reporting.

Perfect Portal

Company (linked to Party)

maps to

Nutshell

Company

1:1
Fully supported

Perfect Portal Parties can be associated with a Company record. If a company is present, it migrates to Nutshell's Company object (Name, Website, Industry, Phone). The Party-to-Company link is preserved as a Person-to-Company relationship in Nutshell. If no company is present on the Perfect Portal party, the person migrates without a Company association.

Perfect Portal

Event (matter-level)

maps to

Nutshell

Activity

1:1
Fully supported

Perfect Portal events attached to a matter (e.g., court dates, deadlines, client meetings) migrate to Nutshell Activities linked to the corresponding Deal. Event type, start datetime, end datetime, description, and assigned user all map to Nutshell Activity fields. Completed vs. pending status is reflected in the Nutshell Activity's completed flag.

Perfect Portal

Document Reference

maps to

Nutshell

Attachment

1:1
Fully supported

Perfect Portal document references are file URLs or stored files attached to a matter. We download each file and re-attach it to the corresponding Nutshell Deal or Person record. File name, file type, and upload datetime are preserved. Large documents are uploaded within Nutshell's per-file size limits (currently 100 MB per attachment).

Perfect Portal

Custom Matter Field

maps to

Nutshell

Custom Field (Deal)

1:1
Fully supported

Perfect Portal matter-type fields that are not native Nutshell Deal fields are created as custom fields on the Nutshell Deal object. Field type is mapped: text to string, number to number, currency to currency, date to date, and dropdown to choice. The custom field is created before the migration run so data can populate during import.

Perfect Portal

Custom Party Field

maps to

Nutshell

Custom Field (Person)

1:1
Fully supported

Perfect Portal party-type custom fields (e.g., bar number, licensing jurisdiction, referral source) are created as custom fields on the Nutshell Person object prior to migration. Each field's data type determines the Nutshell field type. Custom field metadata is exported from Perfect Portal and used to pre-create fields in Nutshell via the API.

Perfect Portal

User / Owner

maps to

Nutshell

User

1:1
Fully supported

Perfect Portal users assigned as matter owners or responsible parties are resolved by email match against Nutshell users. Unmatched owners are flagged before migration so your team can either invite them to Nutshell or assign their matters to a fallback user. No deal lands without a Nutshell owner assigned.

Perfect Portal

Billing / Invoice Record

maps to

Nutshell

Custom Field (Deal) + Note

1:1
Fully supported

Perfect Portal's per-matter billing entries (invoice amounts, payment status, outstanding balance) have no direct Nutshell equivalent — Nutshell does not have native billing or invoice objects. We preserve billing data as custom currency fields on the Nutshell Deal and attach a structured note summarizing the billing history. For full billing reconstruction, your team should use a dedicated accounting tool post-migration.

Perfect Portal

Client Portal Settings

maps to

Nutshell

No Equivalent

1:1
Fully supported

Perfect Portal's client-facing portal configuration (portal access rules, notification templates, client-facing stage visibility) has no Nutshell equivalent. We export the portal settings as a structured JSON reference document so your team can evaluate Nutshell's sharing settings and built-in email notifications as a replacement 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.

Perfect Portal logo

Perfect Portal gotchas

High

No public API or documented export endpoint

High

Third-party access complicates data residency and privilege

Medium

Matter stages are defined per-firm and non-standardised

Low

SMS notification logs are not independent records

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

  • Matter-stage to pipeline-stage mapping requires a manual stage-definition review

    Perfect Portal stages are workflow-driven per matter type and may have non-linear progression (e.g., a matter can skip from Intake directly to Closed). Nutshell pipeline stages follow a linear pick-list sequence by default. Before migration, your team needs to confirm which Perfect Portal stage names map to which Nutshell pipeline stages, and whether any matter-type uses non-standard stage ordering that needs to be preserved as a custom field note. FlitStack delivers a stage-mapping worksheet during the planning phase so this decision is made before any data is written.

  • Perfect Portal's per-matter billing records have no Nutshell equivalent

    Perfect Portal tracks invoice amounts, payment status, and outstanding balances per matter. Nutshell does not have a native billing or invoice object — it is a CRM, not an accounting tool. We preserve billing fields as custom currency and pick-list fields on the Nutshell Deal and attach a structured billing summary note, but your billing data will need a dedicated accounting system post-migration. FlitStack exports the full billing history as a JSON reference so your finance team can reconstruct records in your accounting tool of choice.

  • Document files must be individually re-uploaded; file URLs may expire

    Perfect Portal stores document references as URLs pointing to the law firm's document management system. If those URLs require authentication or expire after a certain period, the files may not be retrievable after the migration window. We recommend downloading all referenced documents before migration begins and uploading them to a shared location (e.g., Google Drive or Dropbox) that Nutshell can access for re-attachment. FlitStack will flag any URLs that return authentication errors during the extraction phase so your team can resolve them before the migration run.

  • N:N party-to-matter associations collapse to primary-party links

    Perfect Portal allows multiple parties of the same type on a single matter (e.g., multiple defendants or multiple co-counsel). Nutshell Deal-to-Person associations are typically 1:N — one primary person per deal. We migrate the primary party as the deal association and surface secondary parties as Nutshell Person custom fields listing their matter involvement. Your team decides whether to create additional deal associations manually post-migration or consolidate to one primary party per deal.

  • Client portal settings and notification rules have no Nutshell equivalent

    Perfect Portal's client-facing portal — which lets clients see matter status, receive SMS notifications on stage changes, and grant access to third parties like real estate agents — is a legal-specific feature with no direct Nutshell equivalent. Nutshell does not support a client portal by default. We export the Perfect Portal portal configuration as a structured reference JSON. If a client-facing view is required post-migration, your team would need to evaluate Nutshell's sharing settings, third-party portal tools, or a dedicated legal client portal product.

Migration approach

Six steps for a successful Perfect Portal to Nutshell data migration

  1. Audit Perfect Portal data and map matter types to Nutshell pipelines

    FlitStack extracts a full data inventory from Perfect Portal via API — parties, matters, events, document references, and all custom fields. We cross-reference each matter type with Nutshell's pipeline model and flag which matter types should map to which Nutshell pipelines. We deliver a stage-mapping worksheet for your team to confirm Perfect Portal stage names to Nutshell stage values before any mapping is committed.

  2. Pre-create Nutshell custom fields and resolve user assignments

    Before importing data, FlitStack creates all required custom fields on Nutshell People, Companies, and Deals via the Nutshell API. We also run an owner-resolution pass: Perfect Portal user emails are matched against Nutshell user accounts. Unmatched users are flagged in a pre-migration report so your team can invite them to Nutshell or assign their records to a fallback owner before the migration run.

  3. Migrate Companies and People first, then Matters as Deals

    The migration is sequenced to respect foreign-key dependencies: Nutshell requires Companies to exist before People (for the Person-to-Company link) and People before Deals (for the deal association). FlitStack migrates in the correct order — Companies, then People with party-type and role fields, then Matters as Deals with stage mapping, then Events as Activities, then Document files as attachments. Each batch is validated before the next begins.

  4. Run sample migration with field-level diff and team review

    A representative sample — typically 100–500 records spanning multiple matter types and party roles — migrates first to validate the entire process. FlitStack generates a comprehensive field-level diff comparing the source Perfect Portal values against the resulting Nutshell records. Your team can verify stage mapping accuracy, custom field population, owner resolution, and document attachment completeness during this pilot phase. Any mapping adjustments, field corrections, or stage-configuration changes identified during review are implemented before the full migration run proceeds.

  5. Execute full migration with delta pickup and rollback readiness

    The full migration runs against Nutshell. A delta-pickup window of 24–48 hours after the primary run captures any Perfect Portal records modified during the cutover. FlitStack maintains an audit log of every record created and updated. If reconciliation identifies missing or mismatched data, one-click rollback reverts the Nutshell instance to its pre-migration state. Post-migration, we deliver a reconciliation report comparing record counts and field completeness between Perfect Portal and Nutshell.

Platform deep dives

Context on both ends of the pair

Perfect Portal logo

Perfect Portal

Source

Strengths

  • Purpose-built for law firm matter-stage visibility with configurable workflow stages.
  • Built-in SMS notification automation tied to stage completion events.
  • Third-party referrer access and commission transparency without additional software.
  • Clean client-facing portal that reduces inbound status calls to the firm.
  • Linked to practice management system so matter data is not duplicated manually.

Weaknesses

  • No documented public API for automated data extraction or migration tooling.
  • Tightly coupled to the host practice management system; switching PMS may break or require reconfiguration of the portal.
  • Third-party access to privileged matter data creates confidentiality governance overhead.
  • Per-matter client pricing lacks transparency and may not scale cost-effectively for high-volume firms.
  • Data residency and security controls for confidential legal matter data in a cloud portal are not publicly documented.
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 Perfect Portal 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

    Perfect Portal: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

Estimate your Perfect Portal 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 Perfect Portal to Nutshell data migrations

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

Can't find your answer?

Walk through your Perfect Portal to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most Perfect Portal to Nutshell migrations complete in 48–72 hours of clock time for firms with under 25,000 total records. Firms with over 200,000 records, complex custom field configurations across multiple matter types, or extensive document libraries extend to 5–7 days. The stage-mapping planning phase — where your team confirms how Perfect Portal stages map to Nutshell pipeline stages — is typically the longest pre-migration step, running 1–3 business days in parallel with other setup work.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Perfect Portal.
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