Migrate from BlueCamroo to Zoho CRM

BlueCamroo Organizations are the parent container for all sub-records and map directly to Zoho CRM Accounts. We import Organizations first in every migration, use the Organization name or domain as the dedupe key, and capture the exported BlueCamroo Organization IDs for use as foreign keys when importing People, Opportunities, Cases, and Projects. The BlueCamroo Organization address, industry, and annual revenue fields map to Zoho Account fields of the same names.

BlueCamroo People are sub-records under Organizations and map to Zoho CRM Contacts. The exported Organization ID must be present in the import file as the Account Name lookup value so Zoho resolves the Contact-Account relationship at import time. BlueCamroo contact fields (email, phone, title, address, custom properties) map to Zoho Contact fields. We sequence this import second, after Accounts are confirmed loaded.

BlueCamroo Opportunities map to Zoho CRM Potentials. The Opportunity name, amount, closing date, probability, and pipeline stage map to Zoho Potential name, Amount, Closing Date, Probability, and Stage. The Organization lookup resolves to the Account lookup in Zoho. BlueCamroo pipeline stages map to Zoho Stage values, and we configure the stage mapping before migration begins so Closed-Lost and Closed-Won statuses land in the correct Zoho stage.

BlueCamroo Cases map to Zoho CRM Cases. Case status (Open, In Progress, Closed, Re-Opened) maps to Zoho Case Status. The Organization lookup resolves to Account in Zoho, and the contact lookup resolves to Contact. BlueCamroo email-to-ticket routing is set via Workflow Rules that do not migrate — we document the active routing configuration during discovery and include it in the Workflow rebuild checklist.

BlueCamroo Projects are full work records with Stages, Tasks, Time Entries, and billing. We map project-oriented records to Zoho CRM Cases when the use case is account-level work tracking, or to Zoho Projects (a separate Zoho product) when the use case requires task dependencies, Gantt views, and billable hour tracking. The decision is made during scoping based on the customer's project type distribution. BlueCamroo project templates export as structural metadata and we include a template inventory in the handoff document.

BlueCamroo Tasks exist within Projects and across the CRM as standalone to-do items. They map to Zoho CRM Tasks with Status, Priority, Due Date, and Description preserved. Parent-project linkage maps to a Zoho Case or Projects lookup depending on the project routing decision. Assignee mapping resolves via email match against Zoho Users. BlueCamroo Task notifications are not recreated during import — we deliver a checklist of active notification rules for manual rebuild in Zoho Blueprint.

BlueCamroo Products and Price Books map to Zoho CRM Products. Product name, SKU, unit price, and description migrate to Zoho Product name, Part Number, Unit Price, and Description. Price Book tiers map to Zoho Product details or a custom price field depending on the customer's pricing model complexity. Products are imported before Opportunities so that line items on Opportunities can reference valid Product IDs.

BlueCamroo Time Entries with billable/unbillable flags, hours, and project linkage do not have a direct Zoho CRM equivalent. We map them to a Zoho Tasks with custom fields for hours logged, billing status, and project reference, or to a custom Time Entries module pre-created in Zoho Setup. The mapping type is confirmed during scoping based on whether the customer relies on time tracking for billing or purely for internal reporting.

BlueCamroo Extra Data Objects (pre-version 8.3.10) and Custom Forms (8.3.10+) both map to Zoho CRM Custom Modules. We query both API endpoints during discovery to ensure no custom data container is missed. Each BlueCamroo Extra Data Object or Custom Form becomes a Zoho Custom Module with the same field structure, custom field types mapped to Zoho field types, and lookup relationships to Accounts, Contacts, or Potentials pre-configured before import.

BlueCamroo Invoices generated from project costs or stage percentages map to Zoho Invoice if the customer licenses Zoho Books, or to a custom Invoices module in Zoho CRM if they do not. Invoice number, date, amount, payment status, and linked customer portal data migrate as custom fields. We determine the correct destination during scoping based on the customer's Zoho product stack.

BlueCamroo per-module user roles map to Zoho CRM Roles and Profiles. We extract the BlueCamroo role assignments during discovery, map each BlueCamroo module access level to a Zoho Role with corresponding module permissions, and deliver a role mapping document. Any BlueCamroo user without a matching Zoho User is held in a reconciliation queue for the customer's admin to provision before record import begins.

BlueCamroo Workflow Rules are configuration records that cannot be exported via the API or Reports. We document every active Workflow Rule during discovery — capturing trigger, conditions, actions, and step sequence — and deliver a written rebuild guide mapped to Zoho Workflow Rules and Blueprint. The customer's admin rebuilds automation logic in Zoho post-migration. This object has no data migration; it is listed for transparency and scope-setting.