Migrate from Fergus to Twenty CRM

Fergus Customer records with an individual name map directly to Twenty People. Standard fields transferred include first name, last name, email address, phone number, and job title. FlitStack performs deduplication checks to ensure that multiple site contacts existing under one organization do not create duplicate People records in Twenty.

Fergus Customers that represent organizations — identified by having multiple sites or jobs associated with the account — split into Twenty Companies. Individual contact records under that customer become Twenty People linked via companyId. FlitStack resolves this by checking for multiple site records on one Fergus Customer.

Fergus Site stores location address, contact name, and phone as a separate entity from the Customer record. FlitStack identifies the primary site by usage frequency or customer-set default, then merges its address into the Company record's address fields. Secondary sites attach as additional address Notes labeled with site name, or as a custom Address relation object if your Twenty workspace employs that pattern.

Fergus Job maps to Twenty Task linked to the parent Company or People record. Job title, description, scheduled date, and assigned technician transfer. Fergus job status (Pending, In Progress, Completed) maps to Twenty Task status (To Do, In Progress, Done).

Fergus Quote with line items and total amount maps to Twenty Opportunity. The Opportunity Name pulls from the Quote title or related Job name. Quote amount becomes Opportunity.amount, and Quote stage (Draft, Sent, Accepted, Lost) maps to Opportunity.stageName pick-list values.

Fergus Invoice has no direct equivalent in Twenty's standard objects. FlitStack migrates invoice total, balance due, and payment status as custom fields on the linked Opportunity record. The invoice line items become Notes attached to the Opportunity for audit trail purposes.

Fergus Asset records (equipment, serial numbers, maintenance schedules) migrate to a Twenty custom object named 'Asset'. Fields for asset name, type, serial number, and last service date transfer. The Asset links to the Company record via a relation field created during migration setup.

Fergus Pricing Tiers assign customer-specific material markup percentages and labor rate overrides. FlitStack migrates the assigned tier name as a custom pick-list field (Pricing_Tier__c) on the Twenty Company record. Tier rate tables — the actual percentage markups and rate overrides — require manual rebuild in Twenty's workflow conditions or a connected pricing calculator tool.

Fergus Supplier records map to Twenty Companies with a custom 'Supplier' type label. The supplier's contact name, email address, and standard payment terms transfer directly. Supplier Companies link to Purchase Order records via Opportunity or custom object relations for downstream purchasing workflow continuity.

Fergus Purchase Orders attach to Jobs and link to Supplier records for material sourcing. FlitStack migrates PO number, total amount, current status, and linked supplier reference to a custom Purchase Order object created in Twenty. PO line items transform into Notes attached to the Purchase Order record for complete audit trail preservation.

Fergus file attachments on Jobs, Quotes, or Invoices are downloaded from storage and re-uploaded to Twenty Notes linked to the parent record. Image files and PDF documents store as attachments within the Note body for native viewing. File size limits imposed by Twenty's storage configuration apply to this migration step.

Fergus Users and assigned Technicians resolve by email address match against Twenty Workspace Members. Unmatched users are flagged in the migration report before processing — your team must invite them to Twenty first, or FlitStack assigns their records to a designated fallback workspace member.