Migrate from Notifi to HubSpot

Notifi contact fields (firstname, lastname, email, phone, address) map directly to HubSpot contact properties. HubSpot's contact model requires an email as the unique identifier — contacts without email are flagged before migration for manual resolution. Phone numbers and addresses migrate as-is with standard HubSpot property types.

Notifi company records (business name, domain, industry, employee count) map to HubSpot company properties. Notifi's residential vs. commercial customer distinction migrates as a custom company property. Industry classification maps to HubSpot's standard industry pick-list with fallback to 'Other' for non-standard values.

Notifi's N:N contact-to-company associations map to HubSpot's native contact-company association. The primary company on a Notifi contact becomes the primary company association in HubSpot. Multiple company associations are preserved with ranking order for each contact.

Notifi job records become HubSpot deals. The job name maps to deal name; job status (scheduled, in-progress, completed, cancelled) maps to deal stage via value mapping per pipeline. Job type and service category migrate as custom deal properties. The job created date preserves as the deal created date.

Notifi's job_type and service_category fields have no native HubSpot equivalent. We create Job_Type__c and Service_Category__c custom properties on the deal object and populate them from the source job record. Pick-list options are defined based on actual values found in the Notifi export.

Notifi estimates map to HubSpot deals with associated quote records. Estimate line items migrate as deal line items. Deposit amounts and estimate status (sent, accepted, declined) preserve as custom properties on the deal. Historical estimate versions are preserved as deal activity notes.

Notifi invoices become HubSpot deals marked as closed-won. Invoice total, balance due, and payment status map to deal amount and custom payment-status properties. Line items from invoices migrate as deal line items. Partial payment status is preserved for reconciliation purposes.

Individual payments on an invoice map to deal line items with a payment_type property. Payment date, method (card, check, cash), and amount preserve as custom line-item properties. Full payment history visible in the deal timeline with each payment recorded as a separate line item entry.

Notifi technicians, dispatchers, and admins resolve by email match to HubSpot users. Unmatched team members are flagged — your team either creates HubSpot users first or assigns records to a fallback owner before migration. Role information is preserved in the user record notes field.

Notifi call records (duration, direction, timestamp, associated contact) migrate as HubSpot engagement calls on the contact record. Call disposition and notes map to HubSpot call outcome and body fields. Multiple calls per contact are preserved in chronological order on the engagement timeline.

Notifi SMS threads migrate as HubSpot engagement records on the contact timeline. HubSpot does not have a native SMS object at the CRM level — texts appear as internal notes with an 'sms' tag for identification. Thread continuity is preserved by grouping messages by conversation.

Notifi job photos and attachments re-upload to HubSpot Files and attach to the corresponding deal record. File size limits apply (HubSpot default 25MB per file). Job photos attach to deal; customer attachments attach to contact. Original file names are preserved for reference.

Notifi custom job fields (equipment_serviced, warranty_status, priority_level, etc.) create as HubSpot custom properties on the deal object. Custom field type (text, number, pick-list, date) is preserved per source field definition. Options for pick-list fields are populated from actual values found in Notifi.

Notifi's scheduling and dispatch calendar does not map to HubSpot's CRM model. Scheduled appointments must be rebuilt using HubSpot Meetings or a third-party scheduling integration post-migration. Historical appointment data migrates as deal activities with timestamps and technician assignment preserved.

Notifi's native QuickBooks sync and billing integration do not have HubSpot equivalents. Accounting and billing data must be managed in QuickBooks or a connected ERP. HubSpot's Payments product handles future payment collection separately and requires independent setup post-migration.