Migrate from Fireberry to Freshsales

Fireberry Contact records map directly to Freshsales Contact. Standard fields (name, email, phone, address, owner assignment) map to Freshsales Contact fields with the same semantics. Fireberry lifecycle stage data stored as a custom field migrates to a Freshsales custom Contact field for audit and segmentation. Email address is the dedupe key during import.

Fireberry Company records map to Freshsales Account. Business details, industry classification, employee count, and address fields migrate to equivalent Freshsales Account fields. The Company-to-Contact relationship is preserved during migration by importing Accounts first and resolving the AccountId reference when Contacts are imported.

Fireberry Deal records map to Freshsales Deal with standard fields (amount, stage, probability, expected close date, pipeline assignment) migrating directly. Deal stage probability percentages round to Freshsales-allowed values. OwnerId resolves by email match against Freshsales User records during import.

Fireberry pipelines and their stage definitions are extracted during schema discovery and reconstructed in Freshsales as Sales Processes with corresponding stage values. Each Fireberry pipeline becomes a Freshsales Record Type so that stage values remain scoped per business line. Stages with no associated Deals are flagged for the customer to review before activation.

Fireberry activity records (calls, meetings, tasks, notes) migrate to Freshsales Task or Event based on type. Call activities become Task records with call subtype. Meeting activities become Event records with start and end timestamps. Notes migrate as Freshsales Note records linked via ContentDocumentLink to the parent Contact, Account, or Deal. Activity timestamps and owner assignments are preserved.

Fireberry Components that define custom objects (user-defined record containers) migrate to Freshsales custom objects. The schema discovery step enumerates every active Component before migration so no custom object is missed. We pre-create the destination custom object schema in Freshsales, including all custom fields, before importing data. Components that extend standard objects (custom fields on Contact, Deal) are handled as custom fields on the equivalent Freshsales standard object.

Fireberry tags on Contacts and Companies export as flat per-record values. Freshsales supports native tags on Contacts and Accounts. We map Fireberry tags to Freshsales native tags where the tag vocabulary is manageable. For large or unstructured tag sets, we map to a Freshsales multi-select picklist custom field. The customer chooses the strategy during scoping.

Fireberry owner references resolve to Freshsales User records by email match. Any Fireberry Owner without a matching Freshsales User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Fireberry owner records are preserved as historical data but mapped to a system user or left unassigned pending admin decision.

Fireberry file attachments stored against records export as download references. We preserve attachment URLs as a custom text field on the target record. Any attachments hosted internally by Fireberry require re-upload to Freshsales or a linked file storage system post-migration; we flag these in the migration report for manual handling.