Migrate from Plexus Software to Nutshell

Plexus Customer records with company name, address, and industry map directly to Nutshell Company records. Plexus stores one primary contact per customer—that contact's details become the first Nutshell Person linked to the resulting Company record. If the Plexus customer includes additional contact roles, those are migrated as extra Person records under the same Company, preserving role titles for reference.

Plexus contact name, email, phone, and job title move to Nutshell Person fields. Plexus stores secondary contacts as additional Person records, all linked to the same Nutshell Company. Owner resolution happens via email match against Nutshell users. If multiple Plexus contacts share the same email, each is mapped to a separate Person record to avoid data loss.

Plexus quotes with line items, amounts, and status become Nutshell Deals. Quote total amount maps to Deal amount; Plexus quote status (Draft, Sent, Accepted, Lost) maps to Nutshell pipeline stages (Incoming, Proposal, Negotiation, Closed Lost). Line-item descriptions are stored in a custom Deal field for invoice reference.

Plexus work order names and dates migrate as Nutshell Activities or Notes attached to the relevant Company or Deal. Work order status (Scheduled, In Progress, Completed, Invoiced) is stored in a custom field on the Deal since Nutshell has no native job or work-order object.

Plexus job-level data—job type, service category, and custom properties—requires Nutshell custom fields on the Deal object. Job type becomes a custom pick-list field; service category becomes a text field. The Plexus job name is preserved as the Note body on the associated Activity.

Plexus employee records with scheduling and capacity data have no CRM equivalent. Employee names and roles are preserved in a custom field on Person records for owner reference. Scheduling and capacity data cannot be recreated in Nutshell and is documented for external tracking.

Plexus stores customer addresses (street, city, state, zip, country) directly on Customer records. These map to the Nutshell Company address fields without transformation. Multi-location Plexus customers require multiple Company records in Nutshell, each with its own address. For each location, we preserve the full address hierarchy, ensuring that geographic filtering and routing in Nutshell work as expected.

Multi-line Plexus quotes consolidate into the Nutshell Deal amount (sum of all line items). Individual line item descriptions are preserved in a custom field on the Deal for invoice reference. Detailed product or service breakdown requires manual reconstruction in Nutshell's product catalog.

Plexus expense records (vendor, amount, category, date, associated job) do not map to Nutshell's CRM objects. We migrate them as Notes attached to the relevant Company or Deal, flagged with an 'Original Expense Record' label and original date for historical reference.

Plexus scheduling data (employee, date range, block type, capacity utilization) has no CRM equivalent in Nutshell. We migrate schedule block names and dates as Tasks attached to the relevant Person or Company, preserving the schedule overview without recreating capacity or dispatching logic.

Plexus time entries (employee, hours logged, job reference, date) do not map to Nutshell CRM objects. We migrate them as Notes on the relevant Work Order or Company with an 'Original Time Entry' label, employee name, hours, and original date for audit reference.

Plexus workflow rules, triggers, and job-based automation logic cannot migrate automatically. FlitStack exports Plexus workflow definitions as a structured reference document your Nutshell admin can use to rebuild equivalent automation in Nutshell's sequence and task tools. The reference document includes trigger conditions, action steps, and field dependencies, allowing your admin to replicate the logic in Nutshell's automation features or external workflow engines.

Plexus users (employees with login) resolve to Nutshell users by email match. Unmatched Plexus users are flagged before migration—your team either creates Nutshell accounts first or assigns records to a fallback owner. No record lands without a Nutshell owner assignment.

Plexus internal record IDs are stored in a custom field on every migrated record. This enables delta-run de-duplication, audit traceability, and reconciliation against Plexus data after cutover. The custom field is named Source_System_ID__c and is indexed in Nutshell for fast lookups during post-migration audits and future data imports.

Free-form notes attached to Plexus customers, contacts, quotes, and work orders migrate as Nutshell Notes on the corresponding record. Original create timestamps and owning users are preserved. Rich-text formatting is simplified to plain text for Nutshell Notes compatibility. If a note contains embedded images, they are stored as file attachments in Nutshell, linked to the note.