CRM migration
Field-level mapping, validation, and rollback between Less Paper Co. and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Less Paper Co.
Source
Nutshell
Destination
Compatibility
11 of 12
objects map 1:1 between Less Paper Co. and Nutshell.
Complexity
BStandard
Timeline
48–72 hours
Overview
Less Paper Co. and Nutshell operate in different functional domains: Less Paper Co. is a 100%-custom-built field-service management platform focused on work orders, job scheduling, technician dispatch, inventory tracking, and on-site payment collection. Nutshell is a CRM designed for sales pipeline management, contact organization, and sales automation with integrated email marketing. There is no native work-order or field-service object in Nutshell — the migration therefore requires mapping Less Paper Co.'s customer records to Nutshell's Company and Person objects, and converting work orders into a combination of Nutshell Tasks and custom fields. FlitStack AI extracts Less Paper Co. data via its export tools, transforms field-service records into CRM-suitable structures, and loads them through Nutshell's API and bulk-import pathways. We surface Less Paper Co.'s custom properties — work order IDs, service types, signature capture references, line items, and technician assignments — as Nutshell custom fields so your team retains operational context without losing data fidelity. Workflows, payment-processing configurations, and scheduling automations built in Less Paper Co. have no CRM equivalent and must be rebuilt manually in Nutshell or a complementary field-service tool.
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 Less Paper Co. 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.
Less Paper Co.
Customer / Account
Nutshell
Company
1:1Less Paper Co. customer records (business name, address, billing contact) map directly to Nutshell Company records. The primary billing address and company phone migrate as standard address and phone fields. Customers without a business name (residential jobs) become Person records instead.
Less Paper Co.
Contact / Customer Individual
Nutshell
Person
1:1Individual contact records in Less Paper Co. (name, email, phone, mobile) map to Nutshell Person records. Multiple contacts at the same customer business attach to the same Company record. The primary contact flag from Less Paper Co. sets the 'primary contact' flag in Nutshell.
Less Paper Co.
Lead / Prospect
Nutshell
Lead
1:1Less Paper Co. leads that have not yet converted to customers map to Nutshell Leads. The lead source, status, and any assigned technician routing become Nutshell Lead custom fields. Once a lead converts in Nutshell, it generates a corresponding Company and Person record.
Less Paper Co.
Work Order
Nutshell
Task + Custom Fields
1:1Work orders are the core Less Paper Co. object with no direct Nutshell equivalent. FlitStack AI creates a Nutshell Task for each work order, linking it to the corresponding Company and Person. All work-order properties (job type, status, scheduled date, technician, line items, signature reference) become Nutshell custom fields on the Task so the full operational history is preserved.
Less Paper Co.
Work Order Line Item
Nutshell
Custom Field (serialized) on Task
many:1Multiple line items per work order (part number, description, quantity, unit price, tax) merge into a single serialized text custom field on the Nutshell Task. A secondary custom field captures the total work-order amount so it appears in Nutshell reports. The raw line-item structure is preserved in JSON-serialized form for admin reference.
Less Paper Co.
Technician / Staff Assignment
Nutshell
Person (internal) + Activity Log
1:1Less Paper Co. technician assignments on work orders map to a Nutshell Person record for each staff member (with an internal flag). Technician check-in and check-out events become Activity log entries on the related Task with original timestamps. Assignee routing from Less Paper Co. becomes a custom field on the Nutshell Task for reporting.
Less Paper Co.
Inventory Item / Part
Nutshell
Custom Field (text) on Task or Company
1:1Nutshell has no inventory management module. Less Paper Co. inventory items, parts used, and vendor PO references migrate as text custom fields on the related Task. Parts frequently ordered together can be surfaced as a custom pick-list field for future reference, butNutshell will not track stock levels or reorder points.
Less Paper Co.
Work Order Notes / Internal Comments
Nutshell
Note on Task
1:1Less Paper Co. work-order notes and internal staff comments attach to the corresponding Nutshell Task as Notes. Original timestamps and the commenting staff member's name are preserved in the Note record so the full service-history narrative is intact in Nutshell. This preserves operational context, decisions, and customer-facing updates made during job execution that your team can reference without accessing the original Less Paper Co. system.
Less Paper Co.
Signature / Payment Record
Nutshell
File + Custom Flag Field
1:1Less Paper Co. electronic signature images (captured on-device) and payment transaction references upload as Files attached to the related Nutshell Task. A custom boolean flag 'Signature_Collected__c' and a custom text field 'Payment_Reference__c' document the payment status without requiring a native payment integration.
Less Paper Co.
Appointment / Schedule Entry
Nutshell
Activity Log Entry
1:1Less Paper Co. appointment reminders and scheduled visit windows migrate as Activity log entries on the related Task in Nutshell. The original scheduled start/end time and assigned technician appear in the activity record. Nutshell does not have a dispatch calendar, so scheduling context is preserved as informational activity history rather than a live calendar event.
Less Paper Co.
Custom Property (general)
Nutshell
Custom Field
1:1Less Paper Co.'s 100%-custom schema means every installation has unique properties beyond the standard fields above. FlitStack AI audits the source schema, creates a matching Nutshell custom field for each unique property (text, number, pick-list, date, or boolean based on source type), and maps values during migration. All custom fields are created before data loads to prevent import errors.
Less Paper Co.
Attachment / Document
Nutshell
File on related record
1:1Work-order attachments (photos, PDF invoices, uploaded documents) migrate as Files attached to the corresponding Nutshell Task. File size limits from Nutshell's storage apply (25MB per file for standard plans). Large photo sets from field visits download and rehost to Nutshell Files storage.
| Less Paper Co. | Nutshell | Compatibility | |
|---|---|---|---|
| Customer / Account | Company1:1 | Fully supported | |
| Contact / Customer Individual | Person1:1 | Fully supported | |
| Lead / Prospect | Lead1:1 | Fully supported | |
| Work Order | Task + Custom Fields1:1 | Fully supported | |
| Work Order Line Item | Custom Field (serialized) on Taskmany:1 | Fully supported | |
| Technician / Staff Assignment | Person (internal) + Activity Log1:1 | Fully supported | |
| Inventory Item / Part | Custom Field (text) on Task or Company1:1 | Fully supported | |
| Work Order Notes / Internal Comments | Note on Task1:1 | Fully supported | |
| Signature / Payment Record | File + Custom Flag Field1:1 | Fully supported | |
| Appointment / Schedule Entry | Activity Log Entry1:1 | Fully supported | |
| Custom Property (general) | Custom Field1:1 | Fully supported | |
| Attachment / Document | File on related record1: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.
Less Paper Co. gotchas
No published API means migration requires vendor-assisted data extraction
Custom schemas per deployment mean no standard export template
Payment gateway tokens do not carry across platforms
Signature images are stored in platform-specific blob format
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
Schema audit and custom-field plan
FlitStack AI connects to your Less Paper Co. instance (via export file or API access) and extracts the full custom schema — every work-order type, pick-list value, custom property, and relationship. We generate a custom-field creation plan for Nutshell: a list of every Nutshell custom field to create on the Task, Company, and Person objects, with field type, pick-list values, and mapping source. Your Nutshell admin approves and creates the fields before migration runs. This step prevents the most common migration failure — importing data into a schema that has not yet been extended to hold it.
Staff technician setup in Nutshell
Before migrating work orders, FlitStack AI creates Nutshell Person records for every technician and staff member in Less Paper Co., tagged with an Internal_Staff__c custom field. The technician-to-work-order routing links each Task to the corresponding staff Person record. If your team uses role-based routing (e.g., licensed electrician vs. apprentice), those role distinctions become custom pick-list values on the Technician__c field so they are available for Nutshell reporting.
Customer and contact migration with de-duplication
Less Paper Co. customers and contacts (Person records) migrate to Nutshell Company and Person objects. FlitStack AI runs de-duplication logic against existing Nutshell records by email address and business name before inserting. Customers with no business name (residential service calls) land as Person records without a Company link. The primary-contact flag from Less Paper Co. sets the primary flag on the Nutshell Person record. Any email or phone mismatches surface in a pre-migration report for manual resolution.
Work-order migration as Tasks with full custom-property mapping
Work orders migrate as Nutshell Tasks linked to the correct Company and Person. All Less Paper Co. custom work-order properties (job type, line items, signature reference, inventory parts, invoice number, payment status, technician assignment, check-in/out timestamps) populate their corresponding Nutshell custom fields. The original Less Paper Co. work_order_id is preserved in Work_Order_ID__c for traceability. A field-level diff is generated after the test run so you can verify every property landed correctly before committing the full migration.
Attachment and file migration
Work-order attachments (photos, PDF invoices, signature images, uploaded documents) download from Less Paper Co. storage and re-upload to Nutshell Files, linked to the corresponding Task record. Files exceeding 25MB are chunked or rehosted with a reference link stored in a custom field. The audit log records every file migrated with its source URL and Nutshell file ID so nothing is lost during the cutover.
Delta-pickup window and validation report
After the full migration loads, a 24–48 hour delta-pickup window captures any work orders created or modified in Less Paper Co. during the cutover. FlitStack AI generates a validation report comparing record counts, custom-field completeness, and attachment coverage between the source and destination. One-click rollback is available if the reconciliation report shows missing records or data-integrity issues. Your team continues working in Less Paper Co. during the delta window — FlitStack AI uses read-only access so there is no disruption to active field operations.
Platform deep dives
Less Paper Co.
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 Less Paper Co. 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
Less Paper Co.: Not publicly documented.
Data volume sensitivity
Less Paper Co. doesn't expose a bulk API — REST + parallelization used for high-volume runs.
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 Less Paper Co. to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Less Paper Co. 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 Less Paper Co.
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.