Migrate from Fergus to HubSpot

Fergus clients map directly to HubSpot contacts. The primary contact on a Fergus client becomes the HubSpot contact record. Additional contacts linked to the same client are associated via HubSpot's contact-to-contact associations. All client properties (address, phone, email, custom properties) migrate as contact properties.

Fergus jobs map to HubSpot deals because both represent a commercial engagement with monetary value. The Fergus job name becomes the deal name, the job amount becomes the deal amount, and the job phase/status maps to a HubSpot deal stage via value mapping. Phase-specific details (phase entered timestamps, phase notes) are preserved as custom datetime fields on the deal.

Fergus job phases (Quote, Confirmed, In Progress, Completed, Invoiced) map to HubSpot deal stages via per-value mapping. Each phase maps to a specific deal stage, and phase-transition timestamps are preserved in custom datetime fields on the deal so reporting reflects the full project history.

Fergus quotes merge into a HubSpot deal with line items representing each quote line. The quote total maps to deal amount. Fergus's deposit rules and pricing tier logic (material rates, labor rates per tier) are preserved as line-item properties or custom fields on the deal since HubSpot's native quote tool handles pricing differently.

Fergus invoices have no native HubSpot equivalent. We preserve invoice data (invoice number, invoice date, total amount, amount paid, payment status, outstanding balance) as custom fields on the associated deal. If HubSpot Payments is enabled, invoice payment status can be synced post-migration.

Fergus tiered pricing (Residential, Commercial, Preferred) maps to HubSpot lifecycle stages via value mapping. The mapping assigns: Residential → Subscriber, Commercial → Lead, Preferred → Customer. This translation preserves the client classification that existed in Fergus's pricing model within HubSpot's CRM structure, eliminating the need for a separate custom field to track tier information.

Fergus staff members who are assigned to jobs map to HubSpot users by email match. Staff with no HubSpot account are flagged; they can be created as HubSpot users before migration or their job assignments are preserved as a custom field on the deal for manual assignment post-migration.

Fergus site addresses map to HubSpot contact address properties (street, city, state/province, postal code, country). If Fergus stores site as a single text field, we split it into HubSpot's structured address fields. Site name is preserved as a custom property.

Fergus job attachments and photos are re-uploaded as HubSpot Files and attached to the corresponding deal. File size limits (25MB per file in HubSpot) apply; large files are flagged for chunked upload or alternate storage with a link preserved on the record.

Fergus custom properties on clients with no native HubSpot equivalent are migrated as custom contact properties in HubSpot. We map each Fergus property type (text, number, date, picklist) to the corresponding HubSpot property type. Picklist values require value-by-value mapping to ensure the dropdown options align between platforms. Any custom property without a direct HubSpot equivalent is flagged and a corresponding custom property is created in the target portal before migration.

Fergus custom properties on jobs (e.g. trade type, job category, custom flags) are created as custom deal properties in HubSpot. Type-aware mapping applies: text to single-line text, numbers to number fields, dates to date pickers, and picklists to HubSpot picklists with value mapping.

Fergus job notes are created as HubSpot engagement notes on the deal. Timestamps and the staff member who added the note are preserved. Multiple sequential notes from the same job are ordered chronologically by the note timestamp. This ensures that communication history, job context, and staff observations transfer to HubSpot maintaining full audit trail continuity from the original Fergus records.