CRM migration

Migrate from ServeManager to Nutshell

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

ServeManager logo

ServeManager

Source

Nutshell

Destination

Nutshell logo

Compatibility

90%

9 of 10

objects map 1:1 between ServeManager and Nutshell.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

ServeManager organizes data around Jobs, Attempts, Companies, and financial records (Invoices, Payments, Server Payables) for the process-serving vertical. Nutshell uses a standard CRM model: People, Companies, Leads, Deals, and Activities. The migration maps each ServeManager Job to one Nutshell Deal, with attempt history and GPS data stored as custom fields on the Deal since Nutshell has no native multi-attempt event log. Process server contacts land in Nutshell People, with their company role preserved in a custom field. ServeManager's CSV export feeds a JSON-RPC API load into Nutshell, with scoped read access used during cutover to avoid disrupting your operations. Workflows, Zapier integrations, and ServeManager-specific automations do not transfer — they must be rebuilt in Nutshell or elsewhere. A 24–48 hour delta-pickup window captures any new or modified Jobs created during the migration window so your Nutshell instance reflects the final state of ServeManager at go-live. The migration also preserves ServeManager IDs as custom fields on each record, enabling traceability back to the source system and supporting delta synchronization if additional data changes occur after the initial cutover window.

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

ServeManager logo

ServeManager

What's pushing teams away

  • The affidavit and custom document system produces bland, small-font output that requires manual reformatting before court filing, driving process servers to alternatives that produce more polished proof-of-service forms.
  • Stripe integration charges a percentage of the invoice amount on top of Stripe's own fees, meaning larger invoices carry disproportionately high processing costs with no added ServeManager effort — reviewers call this paying twice.
  • Complex software with a steep initial learning curve — G2 reviewers describe it as demanding highly skilled people, though others report that new servers become productive within days once trained.
  • For process servers working outside the US or in non-English-speaking jurisdictions, the platform's feature set is oriented almost entirely toward US legal process and may not map cleanly to international practice needs.

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

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

ServeManager

Job

maps to

Nutshell

Deal

1:1
Fully supported

ServeManager's core unit is the Job — a service request with a client, serve recipient, due date, attempt history, and financial fields. Nutshell's Deal object is the direct equivalent: one Job = one Deal. The Job name becomes the Deal name, the client company becomes the Account, and attempt history, GPS data, and financial totals live in custom fields on the Deal.

ServeManager

Attempt

maps to

Nutshell

Deal custom field (Attempt_History__c)

1:1
Fully supported

ServeManager stores each physical service attempt as a separate Attempt record with timestamp, GPS coordinates, photo, and result. Nutshell has no native multi-attempt event log on Deals. We concatenate all attempts per Job into a structured text custom field on the Nutshell Deal (Attempt_Number, Timestamp, GPS_Lat, GPS_Lng, Result, Photo_URL). Photo proof URLs are stored as a comma-separated list.

ServeManager

Company

maps to

Nutshell

Company

1:1
Fully supported

ServeManager's Company object maps directly to Nutshell Company — name, address, city, state, postal code, phone, and website transfer directly. If the company record in ServeManager contains the serve recipient or the law firm client, both roles can be indicated with a custom field on the Nutshell Company record.

ServeManager

Server Payable

maps to

Nutshell

Deal custom fields (Server_Payable_Amount__c, Server_Payable_Status__c)

1:1
Fully supported

ServeManager tracks what the agency owes each process server per job — the server's fee for completing the service. Nutshell has no native payable object. We store the server payable amount and payment status as custom fields on the Nutshell Deal. The process server's contact record lives in Nutshell People (see row 50).

ServeManager

User (Agency User)

maps to

Nutshell

User

1:1
Fully supported

ServeManager user accounts (agency staff) map to Nutshell user accounts. Resolution happens by email address match. Unmatched ServeManager users are flagged before migration — your Nutshell admin either creates the account first or assigns those records to a fallback Nutshell owner.

ServeManager

Process Server (ServerHub Agent)

maps to

Nutshell

Person or Company

1:1
Fully supported

ServeManager's ServerHub agents are independent contractors who receive job assignments. Their contact details (name, email, phone) live in ServeManager's user system. We create them as Nutshell People records, with a custom field (Role__c = 'Process Server') to distinguish them from clients and internal staff.

ServeManager

Invoice

maps to

Nutshell

Deal custom fields (Job_Fee__c, Payment_Status__c, Stripe_Fee__c)

1:1
Fully supported

ServeManager generates invoices tied to completed jobs. The invoice amount (fee), Stripe processing fee, and payment status transfer as custom fields on the Nutshell Deal. The actual invoice PDF is not stored in Nutshell's native file system — we store the invoice amount and a reference URL for manual retrieval.

ServeManager

Job N:N Company association

maps to

Nutshell

Deal → Account relationship

many:1
Fully supported

ServeManager allows multiple companies (client + serve recipient) to be linked to one Job. Nutshell Deals have a single primary AccountId. We link the law firm or ordering client as the primary Account; the serve recipient's company is stored in a custom field (Serve_Recipient_Company__c) on the Deal for reference.

ServeManager

GPS Coordinates

maps to

Nutshell

Deal custom fields (GPS_Latitude__c, GPS_Longitude__c)

1:1
Fully supported

ServeManager captures GPS coordinates on every service attempt. Nutshell has no native geospatial field type. We store the last successful serve's latitude and longitude as separate decimal custom fields on the Deal. The full attempt-level GPS history is preserved in the Attempt_History__c text field.

ServeManager

Attachment / File

maps to

Nutshell

Note or custom field

1:1
Fully supported

ServeManager attachments (affidavits, proof documents, uploaded files) on Jobs are downloaded and re-uploaded to Nutshell. We attach files to the corresponding Nutshell Deal using Nutshell's file attachment support. Affidavit templates from ServeManager are exported as documents — they must be recreated in Nutshell's template system or stored as shared files.

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.

ServeManager logo

ServeManager gotchas

Medium

Stripe double-fee on large invoices inflates processing costs

High

CSV import requires exact column header matching

High

No public API — all data exchange is CSV-only

Low

Marketing Contacts billing model does not apply but payment processing fees do

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

  • ServeManager attempt history has no direct Nutshell equivalent

    ServeManager's core operational detail is the Attempt record — each physical service attempt with its own timestamp, GPS coordinate, photo proof, and result. Nutshell has no native multi-attempt event log on Deals; a single Deal holds one set of activity timestamps. We concatenate all attempts into a structured text custom field (Attempt_History__c) and store the last attempt's GPS as latitude/longitude custom fields. Your team gains full data portability but loses the native timeline view — plan to review the text field in list view or export to a spreadsheet for operational review.

  • ServeManager's N-to-N job-to-company relationship collapses to a single AccountId

    ServeManager allows multiple companies to be associated with one Job — the ordering law firm, the serve recipient's organization, and any other party can all be linked simultaneously. Nutshell Deals have one primary AccountId. We set the law firm or ordering client as the primary Account on the Deal and store the serve recipient's company in a custom field (Serve_Recipient_Company__c). If your operation relies on tracking all parties per Job as first-class relationships, those secondary associations are preserved as text reference only, not as separate linked records.

  • Process server contacts do not map to a native Nutshell object

    ServeManager's ServerHub agent network means your process servers are stored as user accounts with contact details. Nutshell has no Process Server or Contractor object. We create process servers as Nutshell People records with a custom Role__c field set to 'Process Server'. This gives you a searchable contact list, but process server assignments, availability, and compensation are ServeManager-specific concepts with no native Nutshell home — those operational workflows must be rebuilt in Nutshell or managed outside the CRM.

  • Affidavit templates and legal document workflows do not migrate

    ServeManager's affidavit library and custom document templates are platform-specific features. Nutshell has no native affidavit or legal document generation capability. Any custom affidavit templates, branding configurations, or automated document workflows built in ServeManager must be rebuilt from scratch — either within Nutshell using available template features or in a separate document generation tool. We export the template names and field mappings as a rebuild reference, but the templates themselves cannot be transferred.

  • ServeManager's per-order pricing and Stripe fee data must be preserved manually post-migration

    ServeManager records the exact Stripe fee (2.9% + $0.30) per transaction. This data is stored as a custom field on the Nutshell Deal after migration, but Nutshell has no billing or payment processing module — if you need to track Stripe fees historically for reconciliation, the fee amounts transfer correctly but the ongoing payment processing logic does not. Your accounting workflow for tracking Stripe fees against invoices needs to be managed in your accounting tool post-migration.

Migration approach

Six steps for a successful ServeManager to Nutshell data migration

  1. Export full ServeManager dataset via CSV

    FlitStack AI extracts all available records from ServeManager using the built-in CSV export feature: Jobs, Attempts, Companies, Invoices, Payments, and Server Payables spreadsheets. We review the exported schema, confirm column headers, and identify any records with missing required fields (e.g., Jobs with no primary contact). Any gaps are flagged for your team to complete before migration validation begins. We also validate data consistency across related records, such as ensuring Company IDs referenced in Jobs exist in the Companies export.

  2. Design Nutshell custom field schema

    We create the custom fields required on the Nutshell Deal object to hold ServeManager-specific data: Attempt_History__c (text), GPS_Latitude__c (decimal), GPS_Longitude__c (decimal), Attempt_Count__c (number), Job_Fee__c (currency), Stripe_Fee__c (currency), Server_Payable_Amount__c (currency), Payment_Status__c (pick-list), Server_Payment_Status__c (pick-list), Served_Confirmed__c (checkbox), and Source_System_ID__c (text). A setup plan is delivered for your Nutshell admin to create these fields before data loads. The plan includes field names, data types, pick-list values, and the order in which fields should be created to match our import mapping.

  3. Resolve owners and process server contacts

    ServeManager users and ServerHub agents are matched to Nutshell People by email address. Unmatched contacts are flagged before migration — your team creates the Nutshell account or assigns a fallback owner. Process servers are created as Nutshell People with Role__c = 'Process Server'. All contact records are linked to their respective Companies before Deal migration runs. We also map ServeManager's internal user IDs to Nutshell's Source_System_ID__c field for traceability and to support future delta synchronizations between the systems.

  4. Run sample migration with field-level diff

    A representative slice of 100–500 Jobs migrates first, spanning different statuses (Pending, Completed, Cancelled), service types, and attempt counts. We generate a field-level diff report showing each custom field value, GPS coordinate, and financial total as they land in Nutshell. You verify attempt history formatting, GPS field accuracy, and server payable amounts before the full run is approved. This pilot validation ensures the field mapping logic handles edge cases such as multi-attempt jobs with missing GPS coordinates or Jobs linked to multiple Companies.

  5. Execute full migration with delta-pickup window

    Full migration runs against Nutshell's JSON-RPC API using scoped read access on ServeManager. Your team continues working in ServeManager during the cutover window. A 24–48 hour delta pickup captures any new Jobs or status changes made during the migration run. Audit log records every operation. One-click rollback is available if reconciliation reveals record count or data integrity issues. The delta pickup uses ServeManager_Job_ID__c and last_modified_date fields to identify only records changed since the initial extraction, minimizing redundant data transfer.

Platform deep dives

Context on both ends of the pair

ServeManager logo

ServeManager

Source

Strengths

  • Most established process-serving-specific platform with a strong market position and a documented user base dating back to 2007.
  • Mobile app with offline-capable in-field attempt recording, GPS capture, photo proof, and electronic signature collection all in one tool.
  • Integrated Stripe billing lets law firms and clients pay invoices directly, reducing days-sales-outstanding for the process-serving company.
  • Built-in payroll module tracks per-server payables with configurable rates, automating one of the most time-consuming back-office tasks for small process-serving companies.
  • SOC 2 Type II compliance provides the security posture required by law firms and government agencies who handle sensitive service-of-process data.

Weaknesses

  • Affidavit and custom document output is widely described as bland, small-font, and unprofessional — process servers frequently reformat before filing.
  • Stripe payment fees are percentage-based on invoice total with no cap, meaning large invoices carry disproportionate processing costs plus ServeManager's own transaction cut.
  • Steep learning curve for new users — some reviewers describe it as complex and requiring highly skilled operators, despite others finding it intuitive after training.
  • No publicly documented API or API reference; all data exchange relies on CSV export/import with strict column-label requirements, limiting automated migration options.
  • Highly specialized for US process-serving workflows; limited applicability for international firms or non-legal field-service verticals.
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 ServeManager 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

    ServeManager: Not publicly documented.

  • Data volume sensitivity

    A

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

Estimator

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

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

Can't find your answer?

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

Book a free 30 minute consultation

Most ServeManager-to-Nutshell migrations complete in 48–72 hours of clock time for setups under 10,000 Jobs. Larger datasets with 50,000+ Jobs, complex attempt histories, or extensive financial records extend to 10–14 days. The longest planning step is designing the custom field schema on Nutshell Deals to hold attempt logs, GPS coordinates, and server payable amounts before data validation runs. The actual data transfer via Nutshell's JSON-RPC API typically takes 4–8 hours for typical record volumes, with the remaining time spent on schema setup, validation testing, and delta pickup coordination.

Adjacent paths

Related migrations to explore

Ready when you are

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