CRM migration
Field-level mapping, validation, and rollback between ServeManager and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
ServeManager
Source
Nutshell
Destination
Compatibility
9 of 10
objects map 1:1 between ServeManager and Nutshell.
Complexity
BStandard
Timeline
48–72 hours
Overview
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.
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 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
Nutshell
Deal
1:1ServeManager'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
Nutshell
Deal custom field (Attempt_History__c)
1:1ServeManager 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
Nutshell
Company
1:1ServeManager'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
Nutshell
Deal custom fields (Server_Payable_Amount__c, Server_Payable_Status__c)
1:1ServeManager 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)
Nutshell
User
1:1ServeManager 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)
Nutshell
Person or Company
1:1ServeManager'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
Nutshell
Deal custom fields (Job_Fee__c, Payment_Status__c, Stripe_Fee__c)
1:1ServeManager 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
Nutshell
Deal → Account relationship
many:1ServeManager 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
Nutshell
Deal custom fields (GPS_Latitude__c, GPS_Longitude__c)
1:1ServeManager 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
Nutshell
Note or custom field
1:1ServeManager 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.
| ServeManager | Nutshell | Compatibility | |
|---|---|---|---|
| Job | Deal1:1 | Fully supported | |
| Attempt | Deal custom field (Attempt_History__c)1:1 | Fully supported | |
| Company | Company1:1 | Fully supported | |
| Server Payable | Deal custom fields (Server_Payable_Amount__c, Server_Payable_Status__c)1:1 | Fully supported | |
| User (Agency User) | User1:1 | Fully supported | |
| Process Server (ServerHub Agent) | Person or Company1:1 | Fully supported | |
| Invoice | Deal custom fields (Job_Fee__c, Payment_Status__c, Stripe_Fee__c)1:1 | Fully supported | |
| Job N:N Company association | Deal → Account relationshipmany:1 | Fully supported | |
| GPS Coordinates | Deal custom fields (GPS_Latitude__c, GPS_Longitude__c)1:1 | Fully supported | |
| Attachment / File | Note or custom field1: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.
ServeManager gotchas
Stripe double-fee on large invoices inflates processing costs
CSV import requires exact column header matching
No public API — all data exchange is CSV-only
Marketing Contacts billing model does not apply but payment processing fees do
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
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.
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.
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.
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.
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
ServeManager
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 ServeManager 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
ServeManager: Not publicly documented.
Data volume sensitivity
ServeManager exposes a bulk API — large-volume migrations stream efficiently.
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 ServeManager to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your ServeManager 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 ServeManager
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.