Migrate from Fergus to Nutshell

Fergus contacts map directly to Nutshell People. Fergus stores contact name, email, phone, and address fields in snake_case via the API. We map these to Nutshell's Person fields (name, email, phones, address) preserving original create timestamps and owner email for resolution to Nutshell users.

Fergus company records map to Nutshell Companies. Fergus may store company as a text field on a job rather than a linked record — we extract unique company values, deduplicate, and create Nutshell Company records first so the Person → Company lookup resolves correctly during contact migration.

Fergus has no formal N:N contact-to-company association model. Nutshell requires every Person to link to at least one Company. We create the Company records first, then link each Person to the primary company extracted from the Fergus job context. Secondary company associations are preserved as custom fields.

Fergus Job has no Nutshell equivalent — Nutshell has Opportunities but not a job/project record. We migrate key job fields (job name, job number, status, assigned contact, created date) as custom fields on the related Nutshell Person record. Phase history is preserved as a structured text custom field with original phase names and transition timestamps.

Fergus job phases (e.g., Quote Sent, Site Visit, Materials Ordered, Job Complete) have no Nutshell equivalent. We serialize the phase history — phase name, entered date, entered by — as a structured text custom field (Job_Phase_History__c) on the Person record. Phase templates are documented for Nutshell workflow recreation.

Fergus Quote objects store quote name, reference number, total amount, status, and validity dates as first-class records. Nutshell has no Quote object. We create custom fields on the Person record: Quote_Reference__c, Quote_Amount__c, Quote_Status__c, and Quote_Valid_Until__c. Line items are preserved in a structured custom text field or as a formatted note attachment.

Fergus Invoice records hold invoice number, total amount, amount paid, balance due, status, and payment date. Nutshell has no native Invoice object. We map these to custom fields on the Person record: Invoice_Number__c, Invoice_Total__c, Invoice_Paid__c, Invoice_Status__c, and Invoice_Payment_Date__c. Full invoice line-item detail is preserved as a structured text custom field.

Fergus Pricing Tiers are named discount tiers assigned per customer for material pricing. Nutshell has no pricing tier object. We create a custom pick-list field (Customer_Tier__c) on the Person record, mapping each Fergus tier name to a Nutshell pick-list value. The tier-level discount rate is preserved in an additional custom currency field (Tier_Discount_Rate__c).

Fergus line items (material name, quantity, unit price, markup, total) have no Nutshell equivalent. We aggregate material line items per job and preserve them as structured custom text fields (Job_Materials__c) on the Person record, formatted as a readable list: qty × material name @ unit price = line total. Service line items are handled identically in Job_Services__c.

Fergus activity records (call logs, email references, site visit notes) linked to a job map directly to Nutshell Tasks. We preserve the original subject, description/body, owner email for user resolution, and the original activity datetime. Activities with no job context are linked to the associated Person record.

Fergus owner IDs on jobs and contacts are resolved by email match against Nutshell Users. Unmatched owners are flagged before migration — your team either creates the Nutshell user first or assigns records to a fallback owner. No record lands in Nutshell without a valid OwnerId.

Fergus exposes custom_attributes on jobs, contacts, quotes, and invoices via the API as key-value pairs. Each custom attribute becomes a Nutshell custom field created on the appropriate object (Person, Company) with the matching field type (text, number, date, currency, pick-list). Fergus pick-list values map to Nutshell pick-list options.

Fergus workflows trigger on job phase changes, quote status changes, or invoice events. Nutshell workflows use a different trigger-and-action model tied to Person, Company, and Opportunity state changes. Workflows do not migrate automatically — FlitStack exports the Fergus workflow definitions as a JSON specification document that your Nutshell admin can use as a rebuild reference.

Fergus file attachments on jobs, quotes, or contacts are downloaded and re-uploaded to the related Nutshell Person record as file attachments. File size limits and inline image handling follow Nutshell's attachment constraints. Original file names and upload timestamps are preserved.