Migrate from Fergus to Salesforce Sales Cloud

Fergus customers map to Salesforce Accounts (company-level) with a primary Contact record created from the customer name, email, and phone. The Fergus customer ID is stored as a custom field Source_Customer_ID__c for delta-run de-duplication and traceability back to the original record.

Fergus pricing tier assigned to a customer becomes a custom pick-list field (Pricing_Tier__c) on the Salesforce Account. If tier names are numeric or proprietary, we create a value-mapping table before migration so the pick-list reflects your actual tier names in Salesforce.

Fergus quotes become Salesforce Opportunities. The quote name maps to Opportunity Name, total value maps to Amount, and close date maps to CloseDate. Quote status (draft, sent, accepted, declined) requires a custom Status__c field because Salesforce Opportunity stage alone cannot capture all quote lifecycle states — we recommend a two-field model using Stage for pipeline position and Status__c for quote-specific state.

Each Fergus quote line item (material or labour) maps to an OpportunityLineItem on the Salesforce Opportunity. Product2 records are created from Fergus materials; if a Fergus material has no matching Salesforce product, we create one on the fly with the Fergus material name as the product name and a custom Source_Material_ID__c field.

Fergus jobs map to Salesforce Cases rather than Opportunities because jobs represent work being performed (service requests) rather than sales deals. Job status (scheduled, in-progress, completed, invoiced) maps to Case Status pick-list values — we define a custom status pick-list that mirrors Fergus job stages so your Salesforce Cases track the same operational lifecycle your team already uses.

Jobs that are quote-driven (service contracts or ongoing retainer work) may warrant Opportunity records in addition to Cases for reporting parity with your Fergus pipeline view. We create a custom Job_Type__c field on Case to distinguish reactive service calls (Case only) from contract or project work (Case + Opportunity) so you retain both the operational and financial lens.

Fergus invoices become Salesforce Orders. Invoice status (draft, sent, paid, overdue, voided) maps to Salesforce Order Status values — we configure a Status__c field on Order with pick-list values matching Fergus invoice states. Fergus invoice line items map to OrderItems with the same product and quantity logic used for quote line items.

Fergus staff members are resolved by email to existing Salesforce Users. If a staff member has no corresponding Salesforce user, we create a Contact record (staff-as-contact) with a Staff_Role__c custom field preserving their Fergus role (field tech, estimator, admin). Case and Opportunity owners are assigned to the matched Salesforce User; unmatched staff are flagged before migration so your admin can resolve ownership before the full load.

Fergus materials and products map to Salesforce Product2 records. Each product gets a PricebookEntry on the active Salesforce Pricebook. Fergus material pricing (cost, margin, tier pricing) is preserved as custom fields on Product2 — UnitCost__c, Standard_Margin__c — so your Salesforce users see the same cost context your estimators used in Fergus.

Fergus report definitions and Pay Summary exports do not have native Salesforce equivalents — the report layouts, filters, and grouping logic must be rebuilt using Salesforce Reports and Dashboards. We export Fergus report metadata as a reference JSON so your Salesforce admin can replicate the same views in Salesforce's reporting builder.

Fergus automations (email triggers on invoice status, staff notifications on job assignment, pricing tier auto-apply) do not migrate — they must be rebuilt in Salesforce Flow or Process Builder. We export the automation logic as a structured checklist so your admin can rebuild each workflow in Salesforce's native automation tools with the correct object and field references.