Migrate from Fello to HubSpot

Fello contacts map directly to HubSpot contacts. Each contact property in Fello becomes a corresponding HubSpot contact property. Fello's custom contact properties require HubSpot custom property creation before migration. Primary company association maps to HubSpot's company link on the contact record.

Fello's AI-generated lead score (0–100) has no native HubSpot equivalent. We create a custom number field (Fello_Lead_Score__c or as a HubSpot native property) and migrate the score value. Automation-based scoring rules must be rebuilt in HubSpot's workflow logic post-migration. During the migration, the current score is preserved exactly as it exists in Fello, maintaining your historical lead prioritization while you establish new scoring criteria within HubSpot's behavioral framework.

Fello's TCPA consent flags store proof-of-consent dates and source. HubSpot's subscription and communication consent properties capture opt-in status but not the granular consent-source model Fello uses. We map Fello's consent status to HubSpot's opt-in properties and preserve raw consent data as a custom text field for compliance audit.

Fello companies map to HubSpot companies. Company name, domain, industry, employee count, and annual revenue transfer as direct property mappings. Parent-child company relationships in Fello map to HubSpot's parent company field on the company record. We also handle any custom company properties created in Fello by generating matching custom fields in HubSpot and mapping the data during migration, ensuring complete company intelligence transfers.

Fello deal records map to HubSpot deal records. Deal name, amount, close date, and owner assignment transfer directly. Fello's deal-stage values map to HubSpot pipeline stage values. Each Fello deal pipeline requires a corresponding HubSpot pipeline to be created prior to migration so stage pick-list values map correctly.

Fello's pipeline configuration defines deal stages and order. HubSpot supports multiple pipelines per portal, each with independent stage sets. We create HubSpot pipelines to match Fello's pipeline configuration, preserving stage order and probability values as custom fields where HubSpot's native probability model diverges.

Fello deal stage labels map to HubSpot deal stage values within each corresponding pipeline. If stages differ between Fello and HubSpot, we apply value-by-value mapping. Stage-change timestamps are preserved as HubSpot deal custom datetime properties for reporting continuity. Each stage transition in Fello—including the date and time of moves between stages—transfers as a custom property on the HubSpot deal record, preserving pipeline velocity reports and forecast accuracy.

Fello Smart Workflows do not migrate. They must be rebuilt in HubSpot's workflow builder post-migration. We export a Fello workflow definition document — trigger conditions, action steps, and filter logic — as a rebuild reference for your HubSpot admin or RevOps team.

Fello's automated outreach sequences and email drip campaigns do not transfer to HubSpot. HubSpot Sequences require manual setup: cadence steps, email templates, and enrollment triggers. We export sequence metadata from Fello for use as a specification document during HubSpot Sequence configuration.

Any Fello custom contact properties beyond standard fields require HubSpot custom property creation. We audit Fello's property list pre-migration, generate a HubSpot property creation checklist, and map values during the migration run. Property types (text, number, date, picklist) map to equivalent HubSpot property types.

Files attached to Fello contacts or deals are downloaded and re-uploaded to HubSpot Files. Files associate back to the contact or deal record via HubSpot's file attachment model. File size limits apply per HubSpot's file hosting configuration. We verify each file's integrity after upload and maintain the original file naming conventions to preserve document organization.

Fello workspace owners and users resolve against HubSpot users by email match. Unmatched owners are flagged before migration — your team either creates HubSpot user accounts first or assigns records to a designated fallback owner. No record lands without a valid HubSpot owner assignment.