Migrate from Bloomr to Zoho CRM

Bloomr Contact records map to Zoho CRM Leads. The Bloomr contact's name, email address, phone, and any custom fields discovered during profiling migrate to Zoho Lead fields (First_Name, Last_Name, Email, Phone) plus custom fields. If Bloomr stores contacts with a resolved company relationship, the company name maps to the Company field on Zoho Lead. We use email as the dedupe key during import to prevent duplicate records. If Bloomr does not expose a last_name field (e.g., uses a single full-name field), we split on the first space and flag records requiring manual review.

Bloomr Company records map to Zoho CRM Accounts. We map company name to Account_Name, domain to Website, and address fields to the standard Zoho address compound field. If Bloomr stores industry, employee count, or annual revenue, those map to the corresponding Zoho Account fields or to custom fields. Accounts are imported before Contacts so that the Account lookup relationship is satisfied at Contact insert time.

Bloomr Deal records map to Zoho CRM Deals. We map deal name to Deal_Name, deal value to Amount, stage to Stage (with value mapping between Bloomr stage names and Zoho stage names defined during profiling), expected close date to Closing_Date, and owner to the Zoho User via email lookup. Deals without a linked Contact or Account are imported as standalone Deals and flagged for the customer's admin to associate post-migration.

Bloomr pipeline stages map to Zoho CRM Deal stages. We configure the Zoho Sales Process and stage values ( Prospecting, Qualification, Proposal/Price Quote, Negotiation, Closed Won, Closed Lost) before migration. Any Bloomr custom stage names require value mapping to a corresponding Zoho stage or creation of a custom stage in Zoho before import.

Bloomr User records map to Zoho CRM Users via email match. Bloomr owner references on Contact, Company, and Deal records are resolved by matching the owner's email against the Zoho User table. If a Bloomr owner has no matching Zoho User, the record is imported with the Owner field empty and flagged in the reconciliation report. Zoho User provisioning is the customer's responsibility before migration begins.

Bloomr activity records (calls, emails, meetings, tasks) map to Zoho CRM Tasks (with Task_Type differentiating call, email, and task) and Events. Activity subject, date, and notes migrate directly. The linked Contact or Deal is resolved via Bloomr's record ID cross-referenced against the imported Zoho record. If Bloomr does not expose activity data via API or export, activity migration is excluded from scope with a flag in the discovery report.

Bloomr custom fields on the Contact object map to Zoho CRM custom fields on the Leads module. We discover all Bloomr custom field names, types, and values during the API exploration phase and create matching custom fields in Zoho before import. Field types are mapped (text to varchar, number to integer, date to date, picklist to picklist with value mapping). Custom fields without a matching Zoho type are stored as text.

Bloomr custom fields on the Deal object map to Zoho CRM custom fields on the Deals module. The same field type mapping logic applies. Custom fields that represent currency values in Bloomr are mapped to Zoho Currency fields with the customer's base currency configured in the Zoho organization settings before migration.

Attachment and file storage access in Bloomr is unconfirmed. Bloomr's API documentation does not reference attachment endpoints, file storage APIs, or any mechanism for retrieving files linked to contacts, companies, or deals. We do not include attachment migration in standard scope until file access is confirmed through API exploration. If files are accessible as URLs in Bloomr export data, we document them in a separate attachments inventory for the customer's admin to re-attach in Zoho manually or via a separate file migration task.

Bloomr workflows, automation triggers, and lead routing logic are not accessible via any documented export mechanism. We cannot migrate these as structured data. We deliver a written workflow audit template during discovery that captures trigger conditions, actions, and delays from the Bloomr UI. The customer's Zoho admin rebuilds automations using Zoho Blueprint (visual process automation) and Workflow Rules. This is outside standard migration scope.