Migrate from Fireberry to HubSpot

Direct map. Fireberry contact properties migrate as HubSpot contact properties. Fireberry's custom contact fields create HubSpot custom contact properties (requires Enterprise if custom property count exceeds 20 on lower tiers). Original create date preserved as a custom datetime field since HubSpot's Createdate reflects migration time.

Fireberry allows direct contact-to-deal linking. HubSpot uses association labels (Decision Maker, Champion, etc.) on the deal record. We map Fireberry's contact-deal links to HubSpot deal associations and preserve the role label as a custom pick-list value on the association if your HubSpot plan supports it.

Fireberry companies map 1:1 to HubSpot companies. HubSpot's company object uses Name, Domain, Industry, Phone, Address, and Number of Employees as standard fields. Parent-company hierarchies in Fireberry map to HubSpot's parent company field. Multi-company contacts collapse to a single primary company with additional companies listed on the contact's associated companies.

Fireberry deals map to HubSpot deals (Opportunity in HubSpot's internal object model). Each Fireberry deal pipeline becomes a HubSpot deal pipeline. Deal stage values map value-by-value to HubSpot pipeline stages. Closed-won and closed-lost states are preserved with their original close dates.

Fireberry stage names map to HubSpot pipeline stage names per pipeline. Probability values associated with stages in Fireberry are stored as custom number fields in HubSpot since HubSpot's stage probability is pipeline-configured on the backend. Stage-transition timestamps are preserved as custom datetime fields for reporting continuity.

Fireberry call logs migrate as HubSpot engagement activities on the associated contact record. Original call date, duration, outcome, and owner are preserved. Notes associated with the call append to the contact's engagement timeline. Call recordings, if stored in Fireberry, are transferred as file attachments linked to the engagement record.

Fireberry email logs migrate as HubSpot email engagements. Subject, body, timestamp, and owner are preserved. HubSpot's marketing email sending is separate from logged email history—both are handled correctly based on the email type in Fireberry. Attachments embedded in emails are likewise transferred to HubSpot's file storage and linked to the engagement record.

Fireberry meeting records migrate as HubSpot meeting engagements with original start time, end time, title, location, and attendees preserved. Associated contacts in Fireberry link to the same meeting engagement in HubSpot. If meeting notes or agendas are stored, they are migrated as notes attached to the meeting engagement for complete context.

Fireberry notes migrate as HubSpot notes on the associated contact or company record. Rich-text formatting is preserved. Notes without a linked contact or company are attached to the most recently associated company record or held for manual placement. Any tags or categories applied in Fireberry are transferred as custom properties on the HubSpot note for continued organization.

Fireberry custom objects map 1:1 to HubSpot custom objects, but HubSpot requires an Enterprise subscription for custom objects. We deliver a schema plan listing every Fireberry custom object, its fields, and relationships so you can confirm your HubSpot tier before migration. N:N relationships between custom objects in Fireberry require junction objects in HubSpot.

Fireberry owner IDs are resolved by email match against HubSpot users. Unmatched owners are flagged before migration—your team either invites them to HubSpot first or assigns their records to a designated fallback owner. No record lands in HubSpot without a valid owner assignment.

Fireberry file attachments on records are downloaded and re-uploaded to HubSpot Files. Files are linked back to the originating record in HubSpot. File size limits apply (HubSpot's 25MB per file); oversized files are flagged for manual handling. All file metadata such as creation date and owner is preserved during the transfer to maintain audit trails.