Migrate from BlueCamroo to Microsoft Dynamics 365 Sales

BlueCamroo Organizations are the parent container for all sub-records and map directly to Dynamics 365 Account. We import Organizations first in every migration because every other object (People, Opportunities, Cases, Projects) references the Organization as a lookup. We extract the BlueCamroo Organization IDs during export, resolve the mapping to newly created Dynamics 365 Account IDs, and apply that lookup chain when importing child records. This dependency chain is mandatory—importing a Contact without a pre-existing Account results in orphaned records with no parent to attach to.

BlueCamroo People records live as sub-records under Organizations and map to Dynamics 365 Contact. The export template includes the Organization ID as a linking field so we can set the accountid lookup on Contact at migration time. BlueCamroo supports multiple contact roles per Organization; we map these to Dynamics 365 Contact Roles on OpportunityContactRole if the customer licenses the quoting path.

BlueCamroo Opportunities are sales pipeline records linked to Organizations. We map pipeline stages to Dynamics 365 Opportunity Stage values, and pipeline assignments map to a Microsoft Dynamics 365 Sales Process or Record Type that we configure before migration. Closed-Lost and Closed-Won reasons from BlueCamroo custom properties become Dynamics 365 fields for audit. Opportunities reference the resolved AccountId from the Organizations mapping phase.

BlueCamroo Cases are support tickets linked to Organizations with a status lifecycle of Open, In Progress, Closed, and Re-Opened. We map case status values to Dynamics 365 Case Status (Active/Resolved) and preserve the original status history as a custom text field. Email-to-case routing is controlled via BlueCamroo Workflow Rules and must be reactivated post-migration in Dynamics 365 Customer Service settings; we document the routing logic in the Workflow Rules rebuild checklist.

BlueCamroo Projects are full work records with Stages, Tasks, Time Entries, and budget tracking. Projects require a Dynamics 365 Project Operations license or a custom Project entity built in Dataverse. We preserve task structure, task dependencies, billable hour flags, and budget totals. BlueCamroo project templates export as structural metadata; these are documented in the handoff checklist rather than auto-migrated since the template format is not portable.

BlueCamroo renamed Extra Data Objects to Custom Forms in version 8.3.10 (October 2022). We query both the Extra Data Object and Custom Form API endpoints during discovery to ensure no custom data containers are missed. Each Custom Object maps to a Dataverse custom table with equivalent fields and lookup relationships to standard entities (Account, Contact, Opportunity). We pre-create the destination schema including all custom fields, relationship definitions, and validation rules before any data import. Customers on BlueCamroo versions prior to 8.3.10 may have records in Extra Data Objects that appear under a different label in the current UI.

BlueCamroo Products and Services lists tied to Price Books with per-account pricing tiers map to Dynamics 365 Product2 records and PricebookEntry rows in the Standard Price Book. ProductCode maps from BlueCamroo's SKU field. We import Products before Line Items or Opportunities so that the product reference is resolved at migration time.

Time logged against BlueCamroo Projects with billable and unbillable flags and hour totals migrate as time entry records linked to the parent Project record. If the customer does not license Dynamics 365 Project Operations, we create a custom Time Entry Dataverse table and document the custom field schema in the handoff. Billable status, hours, and owner assignment all transfer directly.

Each BlueCamroo pipeline becomes a Dynamics 365 Record Type on Opportunity with a corresponding Sales Process that whitelists the relevant stage values. Stage probability percentages migrate from BlueCamroo to Dynamics 365 StageProbability rounded to the nearest integer allowed by the platform. We configure these in the destination org before Opportunity import begins.

BlueCamroo's per-module subscription model assigns users a role with access to specific extensions (CRM, Sales, Projects, Support). We map BlueCamroo user roles to the equivalent Microsoft Dynamics 365 Sales security role (Salesperson, Sales Manager, VP of Sales, or custom role) and flag any role that has access to BlueCamroo modules without a direct Dynamics 365 equivalent so the customer's admin can adjust permissions post-migration.