CRM migration

Migrate from Perfectview to Nutshell

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

Perfectview logo

Perfectview

Source

Nutshell

Destination

Nutshell logo

Compatibility

70%

7 of 10

objects map 1:1 between Perfectview and Nutshell.

Complexity

BStandard

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

The core challenge when moving from Perfectview to Nutshell is the data model difference: Perfectview uses a single Relation object that combines company and contact data, while Nutshell maintains distinct Company and Contact objects as separate entities. We split every Relation into one Company and one or more Contact records using role and address fields to determine correct placement, then resolve parent-record lookups before inserting Contacts. Activities (calls, emails, meetings, tasks) migrate as Nutshell's native activity timeline, and Cases map directly to Nutshell's Case object. Perfectview's built-in invoicing and billing records are flagged for review because invoice numbering standards differ between EU and US systems. Workflows, automations, and any exact-online or mailchimp integration logic do not migrate; we deliver a written inventory of every active rule for the customer's admin to rebuild in Nutshell's workflow builder. Nutshell's tiered pricing (Foundation at $13/user/month through Enterprise at $79/user/month) replaces Perfectview's flat €30/user/month model, and we surface the cost impact during scoping so the team can plan the license transition alongside the data move.

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

Perfectview logo

Perfectview

What's pushing teams away

  • PerfectView lacks presence on major review platforms, making competitive comparison and peer validation difficult for prospective buyers.
  • The product rebranding to Tribe CRM creates uncertainty about roadmap continuity and whether existing customers will be forced onto a new platform.
  • No public API documentation or developer portal means technical teams cannot independently evaluate integration capabilities before purchase.
  • Limited reporting depth compared to global CRM platforms makes it harder for data-driven sales teams to extract actionable pipeline insights.

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

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

Perfectview

Relation

maps to

Nutshell

Company + Contact (split required)

1:many
Fully supported

Perfectview Relations are the primary source object and conflate company and individual contact data. We split each Relation into one Company record (using the Relation's company name and address fields) and one or more Contact records (extracting role, direct phone, and email from the contact-specific subfields within the Relation). Multi-contact Relations require deduplication by email before inserting into Nutshell. The split logic must be validated against a live sample of at least 50 Relations before bulk migration to confirm that address and role fields are consistently populated.

Perfectview

Activity

maps to

Nutshell

Activity (Calls, Emails, Meetings, Tasks)

1:1
Fully supported

Perfectview Activities (calls, emails, meetings, tasks) are well-structured with timestamps and owner references. We map these to Nutshell's activity types preserving the activity type, date, and owner link. The parent Relation is resolved to the split Company and Contact records so that activities attach to the correct Nutshell timeline. Activity ordering is preserved by setting the timestamp fields to the original Perfectview values.

Perfectview

Case

maps to

Nutshell

Case

1:1
Fully supported

Perfectview support Cases migrate to Nutshell's Case object if the destination Nutshell account includes Service Cloud features. Case status, priority, assignee, and conversation history migrate intact. The linked Relation reference is resolved through the Company-Contact split so Cases attach to the correct Nutshell Company record. If Nutshell Service Cloud is not enabled, we flag this during scoping and recommend enabling it before migration or scoping Cases as a separate phase.

Perfectview

Quote

maps to

Nutshell

Quote

1:1
Fully supported

Perfectview Quotes from the Sales module migrate to Nutshell Quotes with line items, pricing, and status preserved. Quote-to-Relation links are resolved through the Company mapping. Quote PDFs and attachments migrate as files linked to the Quote record. Nutshell Quotes require the Quote object to be enabled in the account settings before import.

Perfectview

Lead

maps to

Nutshell

Lead

1:1
Fully supported

Lead records in Perfectview (whether implemented as a distinct object or as a Relation lifecycle stage) migrate to Nutshell Lead with source, status, and score preserved. If Perfectview uses lifecycle stages within Relations rather than a distinct Lead object, we extract all Relations with a non-customer status as Leads and tag the original stage in a custom field for reconciliation.

Perfectview

Invoice

maps to

Nutshell

Invoice (flagged for review)

lossy
Fully supported

Perfectview's built-in invoicing and billing records migrate with line items and payment status. Invoice numbers may conflict with Nutshell's numbering conventions or EU-specific format expectations. We flag all invoice records for customer review before insertion and recommend renumbering or archiving rather than inserting live invoices into Nutshell, which is not a native invoicing platform. The customer decides whether to migrate invoice history as archived records or exclude it from the migration scope.

Perfectview

Document

maps to

Nutshell

File

1:1
Fully supported

Perfectview Documents migrate as files attached to the parent Company or Contact record in Nutshell. Document metadata (name, upload date, file type) transfers. We retrieve documents via API where enabled, falling back to the UI export for bulk downloads. Files exceeding Nutshell's attachment size limits are flagged for alternative handling.

Perfectview

User

maps to

Nutshell

User

1:1
Fully supported

Perfectview User records migrate as Nutshell Users. Owner-to-record links are preserved in the mapping file and reassigned to matching Nutshell users by email match. Any Perfectview user without a matching Nutshell account is held in a reconciliation queue for the admin to provision before record import resumes.

Perfectview

Custom Fields

maps to

Nutshell

Custom Fields

lossy
Mapping required

Perfectview custom fields on Relations and other objects are discovered during the discovery phase and mapped to equivalent Nutshell custom fields. Nutshell supports custom fields on Companies, Contacts, Leads, Deals, and Cases from its Growth tier upward. We pre-create all custom field definitions in Nutshell before any data migration begins, handling data type translation (date, number, text, picklist) from Perfectview's custom field schema.

Perfectview

Workflow (Automations)

maps to

Nutshell

Workflow

1:1
Fully supported

Perfectview does not expose workflow rules, trigger conditions, or automated sequences through any export mechanism. All workflow logic must be documented manually during the discovery phase and rebuilt from scratch in Nutshell's native workflow builder. We deliver a written inventory of every active Perfectview workflow with its trigger, conditions, and actions, annotated with the equivalent Nutshell workflow configuration. Workflow rebuild is outside the data migration scope and is handled separately by the customer's admin or a Nutshell implementation partner.

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.

Perfectview logo

Perfectview gotchas

High

Relations object conflates Companies and Contacts

Medium

Bulk export function caps at 1000 records per operation

Medium

Workflows and automations cannot be exported

Low

API rate limits are not publicly documented

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

  • Relation-to-Company/Contact split requires sample validation

    Perfectview's Relation object combines company and individual contact data into a single record type. When splitting into Nutshell's separate Company and Contact objects, the correct placement of address, phone, and role fields depends on how consistently those fields are populated in the source data. We validate the split logic against a live sample of at least 50 Relations before bulk migration. If address fields are populated on the Relation level rather than the contact subfield level, the Company record may be incomplete. Migrations that skip this validation step produce Contacts without a parent Company and orphaned address data that cannot be re-associated after bulk insert.

  • Perfectview bulk export caps at 1,000 records per pass

    The built-in Perfectview export-to-Excel function limits selections to 1,000 Relations at a time. For databases with thousands of records, this requires multiple export passes using date-range or alphabetical filters to avoid overlap. We automate the chunking process via the API where available or through scripted UI export to ensure complete coverage. Records at boundary points between chunks require deduplication to avoid creating duplicates during import into Nutshell.

  • API rate limits not publicly documented

    Perfectview exposes an API that can be activated in account settings, but the platform does not publish rate limits, quota thresholds, or per-endpoint restrictions. We discover actual limits through a pre-migration load test using a trial account. If rate limits are restrictive, we throttle API reads and use the bulk export function as the primary data source, treating the API as a delta and validation tool rather than the primary read path.

  • Invoicing and billing records may not belong in Nutshell

    Perfectview includes built-in invoicing and billing features. Nutshell is not a native invoicing or accounting platform. Invoice records migrate with their full line item history and payment status, but we recommend reviewing whether live invoice records belong in a CRM rather than an accounting system. If the customer uses Nutshell exclusively as a sales CRM, we recommend archiving invoices rather than inserting them as active records that may conflict with the accounting system's data.

  • EU data residency does not transfer to Nutshell

    Perfectview stores all data in the Netherlands under EU law with explicit GDPR tooling. Nutshell is US-hosted and does not offer EU data residency. For teams with strict EU data-residency requirements (common in Benelux financial services, healthcare, and government sectors), this is a compliance flag that must be raised before migration begins. If EU residency is a hard requirement, Nutshell may not be an acceptable destination without a data-processing agreement covering the cross-border transfer.

Migration approach

Six steps for a successful Perfectview to Nutshell data migration

  1. Discovery and data audit

    We audit the source Perfectview account across Relations (total count, field inventory, role subfield consistency), Activities (call, email, meeting, task volumes), Cases, Quotes, Invoices, Leads, Documents, custom fields, and active workflow definitions. We extract a sample of at least 50 Relations to validate the split logic for Company and Contact extraction. We also assess the Nutshell destination account settings: which plans are active, whether Service Cloud is enabled for Cases, and whether custom fields are available on the current tier. The discovery output is a written migration scope document covering record counts, split logic, custom field inventory, and a Nutshell tier recommendation.

  2. Relation split design and custom field provisioning

    We design the split logic for Relations before any data extraction. For each Relation, the company-level fields (company name, billing address, phone) become a Nutshell Company record, and the contact-specific fields (name, email, role, direct phone) become one or more Nutshell Contact records linked to that Company. We pre-create all Nutshell custom fields in the destination account before migration, mapping data types from Perfectview to their Nutshell equivalents. If Nutshell Service Cloud is not active, we recommend enabling it before migration or excluding Cases from the initial migration scope.

  3. Sample migration and split validation

    We run a sample migration of the first 100-200 Relations (with associated Activities, Cases, and Quotes) into a Nutshell staging environment. The customer reviews the output and confirms that the split logic correctly assigned company data to Company records and contact data to Contact records. Any split errors (Contacts without a parent Company, duplicate Addresses) are corrected in the mapping logic before the full migration begins. This step prevents bulk-record rejection and ensures the split is validated rather than assumed correct.

  4. Full data extraction in chunks

    We extract all Relations from Perfectview using the bulk export function, chunked in batches of up to 1,000 records per pass. Each chunk is processed through the split transform (Relation to Company plus one or more Contacts), deduplicated by email, and written to a staging CSV. Activities, Cases, Quotes, Leads, and Documents are extracted in parallel, with parent-record IDs preserved for cross-object linking. Any Perfectview API calls are throttled based on the pre-migration load test results.

  5. Production migration in dependency order

    We run production migration into the live Nutshell account in record-dependency order: Companies first (as the parent for all Contact lookups), then Contacts (with parent CompanyId resolved), then Leads, Activities (via Nutshell's activity API with timestamp preservation), Cases (if Service Cloud is active), Quotes (with file attachments), Documents (as files), and Invoices (flagged as archive candidates). Each phase emits a row-count reconciliation report. Owner references are resolved by email match against Nutshell users, with mismatches held in a queue for the admin to provision before resuming.

  6. Cutover, validation, and workflow handoff

    We freeze Perfectview writes during cutover and run a final delta migration of any records modified during the migration window. We validate record counts against the discovery audit and spot-check 25-50 records in Nutshell against the source. We deliver the workflow inventory document to the customer's admin team covering every active Perfectview workflow with its trigger, conditions, and a recommended Nutshell workflow configuration. We support a one-week hypercare window for reconciliation issues. We do not rebuild Perfectview workflows as Nutshell workflows inside the migration scope; that is a separate engagement.

Platform deep dives

Context on both ends of the pair

Perfectview logo

Perfectview

Source

Strengths

  • All-in-one CRM covering sales, marketing, support, and billing without requiring third-party integrations for core functions.
  • Netherlands-hosted data with ISO certification and explicit GDPR tooling appeals to EU-regulated industries.
  • Predictable flat pricing model with a permanent discount for the first five users reduces billing surprises.
  • Free helpdesk support is included in all plans with direct access to the PerfectView team in Den Bosch.

Weaknesses

  • Product has been rebranded to Tribe CRM with unclear migration path for existing PerfectView customers.
  • No public API documentation or developer portal limits technical transparency and pre-sales evaluation.
  • Absence from major review platforms (G2, Capterra) means no independent validation of user satisfaction or feature claims.
  • Limited advanced reporting and analytics compared to global CRM competitors makes pipeline intelligence harder to extract.
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. 4 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 Perfectview and Nutshell.

  • Object compatibility

    C

    4 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

    Perfectview: Not publicly documented in summary form..

  • Data volume sensitivity

    A

    Perfectview exposes a bulk API — large-volume migrations stream efficiently.

Estimator

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

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

Can't find your answer?

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

Book a free 30 minute consultation

Most migrations land between three and five weeks for accounts under 10,000 Relations and 2,000 Activity records with no Service Cloud complexity. Migrations with large custom field sets, multi-role Relations requiring multiple Contact splits per Relation, high-volume activity histories, or Cases requiring Service Cloud provisioning move to six to ten weeks because of the split validation work, Activity timeline chunking, and Service Cloud coordination. The split logic validation during the sample migration phase is the most time-critical step and cannot be bypassed without risking incorrect Company-Contact relationships in the destination.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Perfectview.
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