Migrate from Fergus to Zoho CRM

Fergus customers who are prospects or have not yet had a job booked become Zoho Leads. Active customers with a signed quote or completed job convert to Contacts linked to an Account. We use the existence of a Fergus Quote or Job record as the split criterion so no record lands in the wrong module.

Fergus customers with a company name stored become Zoho Accounts with the company name as Account Name, and the customer contact becomes a Contact linked to that Account via Account Name lookup. If Fergus stores multiple contacts per company, the primary contact links; additional contacts import as separate Contact records.

Fergus Sites have no Zoho native equivalent — we create a custom 'Job Sites' module with fields for Site Name, Address, Site Contact Name, Site Contact Phone, and a lookup to the parent Account or Contact. Each Fergus Site ID is preserved as an external ID on the custom module record.

Fergus quotes map to Zoho Quotes with Quote Number, Subject, Account (via lookup), Contact, Valid Till date, and line items migrated as Quote Items sub-form rows. Fergus quote status (Draft, Sent, Approved, Declined) maps via value-mapping to Zoho Quote Status pick-list.

Fergus quote line items (product/service name, quantity, unit price, cost, margin %) become Zoho Quote Item rows. Margin and cost are stored as custom number fields on the sub-form row since Zoho Quote Items do not natively track cost or margin. Markup percentage is recalculated from the migrated cost and unit price fields.

Fergus Jobs map to Zoho Deals. Job Name becomes Deal Name, expected revenue or quote value becomes Deal Amount, and Fergus Job Status (Scheduled, In Progress, On Hold, Complete, Invoiced) maps via value_mapping to Zoho Deal Stage pick-list values. The original Fergus Job Number is preserved as Source_Job_Number__c on the Deal for reconciliation.

Fergus tracks job progress through phases (e.g., Scheduled, En Route, On Site, Parts Ordered, Complete). Zoho has no native phase concept on Deals, so we create a custom pick-list field Job_Phase__c and map each Fergus phase name to a matching pick-list value. Phase-entered timestamps are stored as custom datetime fields per phase.

Fergus staff assigned to jobs have no direct Zoho equivalent since Zoho Users are CRM administrators and salespeople. We create a custom lookup field Assigned_Staff__c on the Deal that resolves by email match to existing Zoho Contacts representing staff members. Unresolved staff are flagged for manual assignment before go-live.

Fergus invoices do not migrate because Zoho CRM has no native invoicing module. Companies that need invoice history in Zoho should use Zoho Invoice as a separate application. We export Fergus invoice records (invoice number, date, amount, line items, payment status) as a CSV reference file that can be imported into Zoho Invoice manually or via a separate Zoho Invoice data migration. Invoice attachments re-upload as Zoho Files linked to the exported invoice reference.

Fergus activity log entries (call summaries, email bodies, internal notes attached to jobs) migrate as Zoho Tasks with Subject, Description, Related To (linked to the corresponding Deal), Owner (resolved by email), and original timestamps. Fergus note attachments re-upload to Zoho Files.

Fergus file attachments on quotes and jobs re-upload to Zoho Files, linked to the corresponding Quote or Deal record. Files are downloaded from Fergus, uploaded to Zoho Files with the original filename and a reference to the source Fergus record ID preserved in a custom field.

Fergus pricing tiers (assigned per customer for material pricing) have no Zoho equivalent. We create a custom pick-list field on the Account or Contact record and map each Fergus pricing tier name to a pick-list value. The tier determines material pricing in Zoho via lookup formulas or manual reference.

Fergus staff who are also CRM users import as inactive Zoho Users with their email and name, linked to Contact records for field assignment purposes. Non-CRM staff are imported as Contacts with a Staff_Role__c custom pick-list field. This ensures job assignments can still reference staff without consuming Zoho user licenses.

Fergus custom fields on any module (e.g., custom properties on Jobs for trade-specific data) migrate to Zoho custom fields on the corresponding module. The Fergus field data type is matched to the nearest Zoho field type — multi-select pick-lists, checkboxes, and numeric fields all map with type-aware conversion.