Migrate from Fireberry to Zoho CRM

Fireberry Contact records map directly to Zoho CRM Contact. Standard fields (name, email, phone, address, owner assignment) map 1:1 to Zoho Contact fields. We resolve the owner assignment by matching Fireberry owner email to Zoho User email during import. Any Fireberry Contact linked to a Company resolves the Zoho Account lookup by Company name as the dedupe key before Contact insert.

Fireberry Company records map to Zoho CRM Account. Business details, industry classification, size, and address fields migrate to the Account standard layout. We create Accounts before Contacts in the import sequence so that the Account-Contact lookup is satisfied at the moment of Contact insert. Account is the dedupe key for Company during import.

Fireberry Deal records map to Zoho CRM Deal. Amount, stage, probability, expected close date, and pipeline assignment migrate directly. We preserve stage ordering and map Fireberry pipeline assignments to Zoho Deal custom fields or pipeline configurations. Any custom Deal fields discovered during schema enumeration migrate as Zoho custom fields on the Deal module.

Fireberry multiple named pipelines with configurable stages require Zoho pipeline reconstruction. We extract pipeline definitions and stage ordering during schema discovery, then create Zoho Pipelines with matching stage names and probability values. Stages with no associated Deals are flagged for the customer to review and optionally remove from the final Zoho configuration.

Fireberry activity notes migrate to Zoho CRM Notes attached to the parent record (Contact, Account, or Deal). Note body, created timestamp, and owner assignment transfer directly. Notes linked to multiple parent records are attached to the primary parent record with a cross-reference to secondary parents in a custom field.

Fireberry call log activities migrate to Zoho Tasks with the Call subtype flag. Call duration, disposition, and recording URL (if stored in Fireberry) migrate to custom Task fields. Activity timestamp becomes the Zoho Task Activity Date to preserve timeline ordering. Owner assignment resolves via email match to Zoho User.

Fireberry meeting activities map to Zoho Events with Start DateTime, End DateTime, and Location preserved. Attendee lists migrate to Zoho Event attendee records. We flag any recurring meeting series because Zoho's recurring event handling differs from Fireberry's and may require manual adjustment post-migration.

Fireberry task activities migrate to Zoho Tasks with Status, Priority, and ActivityDate preserved. Task assignment migrates by resolving the Fireberry owner email to Zoho User ID via the owner mapping table. Overdue tasks retain their original due date and status at migration time.

Fireberry user-defined Components that represent standalone objects map to Zoho CRM Custom Modules. We discover the full Component schema during schema enumeration, pre-create the Zoho custom module with matching field types (text, number, date, picklist, lookup), and import records after all standard object dependencies are satisfied. Lookup relationships between custom Components and standard objects require the referenced standard record to exist first.

Custom fields on Fireberry Contacts, Companies, Deals, and Activities migrate to Zoho CRM custom fields on the equivalent module. Field type mapping follows Zoho's field type schema: picklists, multi-select picklists, dates, numbers, checkboxes, and formula fields are recreated with equivalent Zoho field types. We flag any formula-type custom fields that may require Zoho formula reconfiguration post-migration.

Fireberry tags on Contacts and Companies migrate to Zoho CRM Tags. Tags are stored as flat lists per record. We preserve the tag structure as a comma-separated tag list on each record during import. If the customer uses tags for segmentation, we recommend creating Zoho custom views filtered by tag as a post-migration step.

File attachments stored against Fireberry records are exported as download references. Any attachments hosted internally by Fireberry require re-upload to Zoho's file storage during migration. We preserve attachment URLs in a Zoho custom field so that the customer can re-upload the files and link them manually, or engage a separate attachment migration service for large volumes. External URL attachments (hosted on third-party storage) migrate as a URL field and do not require re-upload.