Migrate from Fergus to HighLevel

Fergus Customers map to both a HighLevel Contact and a HighLevel Company. The contact holds the primary person record (name, phone, email); the company holds business-level data (business name, address). Staff and trade contacts within Fergus become separate Contact records linked to the primary Company.

Fergus stores phone and email as standard contact properties. HighLevel maps these to its native Contact fields during migration, preserving all contact identifiers across systems. If a Fergus customer has multiple phone numbers on file, the additional numbers are created as custom fields on the HighLevel Contact record to preserve the complete contact profile.

Fergus Jobs map to HighLevel Opportunities. Job status (New, In Progress, Scheduled, Completed, Invoiced) maps to a custom Opportunity stage or a custom pick-list field (Job_Status__c) on the Opportunity. Job phases map to custom fields or Opportunity-level notes capturing each phase's status and timestamp.

Fergus Jobs contain named phases (e.g., Survey, Materials Ordered, Installation, Inspection). HighLevel has no native phase concept. We create a custom multi-select or pick-list field Phase__c on the Opportunity and populate it from Fergus phase names. Phase sequence and timestamps are preserved in Phase_History__c as a text audit trail.

Fergus Quotes are distinct from Jobs. Each Quote migrates as a separate Opportunity record in a 'Quote Sent' stage (or a custom 'Quote' stage your admin creates). Line-item details (materials, labour rates) are stored as a JSON-formatted note on the Opportunity since HighLevel lacks native quote line items.

Fergus Invoices have a lifecycle separate from Jobs. We create a custom field Invoice_Status__c on the Opportunity (values: Sent, Paid, Overdue, Void) and migrate invoice records as Opportunity records in an 'Invoiced' stage. The original invoice number and total are stored in custom fields on the Opportunity.

Fergus Pricing Tiers are customer-level pricing rules. These map to a custom pick-list field Pricing_Tier__c on the HighLevel Contact. Tier values (e.g., Trade Standard, Preferred, Wholesale) are recreated as pick-list options. Material-specific pricing within tiers is stored as a text custom field for reference.

Fergus material line items within Jobs have product name, quantity, unit price, and total. HighLevel has no native line-item object. We store material summaries as a text field Materials_List__c on the Opportunity, formatted as a readable list. Detailed line-item accounting remains in your accounting tool (Xero/QuickBooks) post-migration.

Fergus staff records contain name, email, and role information. We match Fergus staff by email to HighLevel User accounts using an automated lookup process. Any staff members without a matching HighLevel User are flagged as Contacts with a custom field Staff_Source__c, allowing you to manually invite them to HighLevel before migration finalization.

Fergus job notes migrate as HighLevel Notes attached to the corresponding Opportunity record. All file attachments such as photos, diagrams, and PDFs are re-uploaded to HighLevel Files and linked to the Opportunity. Original timestamps and author names are preserved within the note metadata for audit continuity.

Fergus does not have a native tagging system, but any custom labels your team applied to Jobs or Customers migrate as HighLevel Tags on the relevant Contact or Opportunity record. Tags are flat — no hierarchical tag structure is needed.

Fergus custom fields on Customers and Jobs map to HighLevel custom fields on Contact or Opportunity depending on object. HighLevel requires you to choose Contact vs Opportunity at field creation — we verify object assignment during the mapping plan phase. Field type mapping: text → text, number → number, date → date, pick-list → pick-list.