Migrate from Fergus to monday CRM

Fergus stores customers as combined person-and-company records. We split them: person fields (name, email, phone) land in monday CRM Contacts; company fields (company name, industry, size) land in monday CRM Accounts. When a Fergus customer has no separate company record, we create a monday CRM Account using the customer name as a placeholder so Contacts always have an Account parent.

Fergus Sites represent physical locations attached to customers—address, city, region, and site-specific notes. We map Sites to monday CRM Accounts with a Site_Flag__c custom column set to TRUE so monday users can distinguish location entities from organization entities. Sites without an existing Account create a standalone Account record with the site address as the primary address.

Fergus Jobs are the core record—job number, description, type, status, priority, assigned employee, customer link, site link, scheduled date, and custom properties. We map Jobs to monday CRM Deals as Items on the designated CRM board. Fergus job status (Active, Scheduled, Completed, Invoiced) maps to a monday CRM Status column with matching values so stage reporting reflects the original workflow. Job number becomes the monday Item Name prefixed with 'JOB-' for traceability.

Fergus Quotes are separate from Jobs but linked to customers and sites. We merge quote data into the corresponding monday CRM Deal Item: quote amount becomes the Deal Amount column, quote status (Draft, Sent, Accepted, Declined) becomes a separate Status column on the Item, and the quote line items migrate as monday CRM Product items linked to the Deal. If a Quote has no corresponding Job, we create a Deal Item with Quote-only flags set via custom columns.

Fergus Invoices carry invoice number, amount, status (Paid, Overdue, Void), and payment date. We attach invoice metadata as monday CRM Deal columns (Invoice_Number__c, Invoice_Status__c, Paid_Date__c) and set a Deal Stage of 'Closed Won' for paid invoices. Unpaid invoices keep their Fergus stage (Draft, Sent) mapped to monday Status values. Monday does not have a native invoice object—financial reconciliation requires linking to an external accounting integration.

Fergus Employees are team members who own jobs. We match Fergus employee email addresses against monday CRM workspace members by email. Unmatched employees are flagged as a pre-migration step—your team either creates monday user accounts first or assigns those records to a fallback owner. Once matched, the Fergus employee's name and role populate the monday People column on Deal Items.

Fergus Pricing Tiers define material rates and labor rates per customer or job type. Monday CRM has no direct pricing-tier object; we translate tiers into monday CRM Product Catalog entries (each tier = one Product with Name, Unit Price, and Description fields) and link them to Deals via line items. If tier assignment logic is complex, we preserve the tier name in a Pricing_Tier__c custom column on the Deal for admin reference.

Fergus job updates and internal notes (timestamped, attributed to employees) migrate as monday CRM Updates on the corresponding Deal Item. We preserve the original author name, timestamp, and full note body. monday Updates are flat per-Item; we format the author as 'Fergus Employee: {name}' to maintain attribution clarity in monday's activity feed.

Fergus custom fields (text, number, date, dropdown, checkbox) per Job, Customer, or Quote map to monday CRM custom columns on the relevant board. We infer column type from Fergus field type: text → Text column, number → Numbers column, date → Date column, dropdown → Status column, checkbox → Checkbox column. Dropdown values require explicit mapping since monday Status columns hold a defined set of options.

Fergus file attachments on jobs (photos, PDFs, signed forms) are downloaded and re-uploaded to monday CRM as Files attached to the corresponding Deal Item. File size limits apply: monday caps uploads at the plan-tier storage limit (typically 5GB on Basic, 20GB on Standard, 100GB on Pro). We flag files exceeding monday's per-upload limit before the migration runs.