Migrate from WennSoft to Nutshell

Equipment has no CRM equivalent — requires custom field strategy

Nutshell has no native Equipment or Asset object. Equipment serial numbers, model numbers, warranty expirations, and maintenance schedules must be modeled as custom fields on the Company record. If you have hundreds of equipment records per customer, this means either storing a JSON blob in one field or creating multiple custom fields — both have tradeoffs for reporting. We deliver a custom field design document before migration so you can pre-create the fields in Nutshell and avoid schema gaps during import. Without pre-planning, equipment history either lands as unstructured text or requires a post-migration cleanup pass.

Work order and service call history inflates task volume significantly

WennSoft customers with active service agreements accumulate thousands of service calls per year. Each call becomes a Nutshell Task, which counts against your Nutshell contact and activity limits depending on your plan tier. A customer with 800 open and closed service calls over five years generates 800 task records. If your Nutshell plan caps activities or if you are on a lower contact tier, this volume affects your plan decision before migration. We flag record counts during the discovery phase and help you scope the migration to exclude closed calls older than a defined threshold if needed.

Billing and invoice data do not migrate — must be handled separately

Nutshell has no invoicing, accounts-receivable, or job-costing module. WennSoft invoices, billing rates, cost-plus calculations, and AR aging reports have no destination object. We export these as CSV files for import into your accounting system — QuickBooks, NetSuite, or Dynamics GP remain the system of record for financial data. This boundary must be explicit before migration: the CRM migration and the financial data migration are separate projects with separate timelines. Reviewers on G2 flag that CRM-only platforms require clear handoffs to accounting tools, which is especially relevant when moving off an integrated ERP like WennSoft.

Service agreement rules and PM schedules have no Nutshell automation equivalent

WennSoft's preventive maintenance scheduling and service agreement escalation rules are GP-integrated workflows. Nutshell has no native scheduling engine for contract-based service reminders. Open PM agreements, renewal dates, and escalation triggers do not migrate as active automation — they are exported as documents and date fields on the Company record for manual follow-up. If your team relies on automatic service call dispatch based on PM schedules, that logic must be rebuilt in a different tool or handled as a process change in Nutshell. We document the PM schedule dates as custom fields so your team can set manual reminders.

Multi-location customers require explicit mapping rules or create duplicate companies

WennSoft supports multiple service locations per customer entity. Nutshell Companies are flat records — if you create a separate Company record for each location, you end up with N companies per former customer, which fragments the account view. We offer two strategies: collapse all locations into one Company with address fields for secondary sites, or create separate Company records with a naming convention your team defines. The choice affects reporting, duplicate detection, and how sales reps see the account. We surface this decision during discovery and apply your chosen rule consistently across all multi-location records during migration.