Migrate from BlueCamroo to Salesforce Sales Cloud

BlueCamroo Organizations map directly to Salesforce Account. The Organization is the root parent record in BlueCamroo's schema; every other record type (Contact, Opportunity, Case, Project) references an Organization. We export all Organizations first, generate Salesforce Account IDs, and build a lookup table mapping BlueCamroo Organization IDs to Salesforce Account IDs. This lookup table is the key dependency that resolves every subsequent record's WhatId or AccountId reference. Organization name becomes Account Name; Industry and Website migrate directly. Annual Revenue and Employee Count map to typed Number fields.

BlueCamroo People are sub-records under Organizations. We import Contacts after the Account lookup table is complete, then set each Contact's AccountId by resolving the BlueCamroo Organization ID to its generated Salesforce Account ID. Email, FirstName, LastName, Phone, and Title migrate directly. BlueCamroo's Contact notes and tags transfer to Salesforce Contact Description and custom multi-select picklist fields. If a Contact in BlueCamroo has no Organization parent (orphaned record), we flag it during scoping for the customer's admin to assign to a default Account or merge before migration.

BlueCamroo Opportunities attach to Organizations and carry stage, amount, probability, and close date. We map Opportunity.StageName to Salesforce StageName by resolving the BlueCamroo pipeline stage value to a matching Salesforce Sales Process stage. Amount migrates as Currency; CloseDate migrates as Date. If BlueCamroo's pipeline includes a stage name not present in the destination Salesforce org's Sales Process, we flag it during scoping and recommend adding the stage before migration begins. OwnerId resolves via the email-lookup User mapping established during owner reconciliation.

BlueCamroo pipeline stages map to Salesforce Sales Process stages. We create a Salesforce Sales Process per BlueCamroo pipeline, whitelisting only the relevant stage values for that pipeline. Stage probability percentages migrate from BlueCamroo to Salesforce StageProbability. If the customer uses multiple BlueCamroo pipelines (Sales, Support, Project-based), each maps to a Salesforce Record Type on Opportunity so that stage values stay scoped per business line.

BlueCamroo Cases are support tickets linked to Organizations with status lifecycle (Open, In Progress, Closed, Re-Opened). We map Case.Status to Salesforce Case Status picklist values, preserving the original BlueCamroo status in a custom field bc_original_status__c. Case priority migrates to Case Priority. If Salesforce Service Cloud is in scope, email-to-case routing is configured separately post-migration; the routing rules are part of the Workflow documentation deliverable. Case comments and internal notes migrate as CaseComments and Salesforce Notes attached to the Case record.

BlueCamroo Projects are full work records with Stages, Tasks, Time Entries, and budget tracking. Salesforce Sales Cloud has no native Project object, so we create a Project__c custom object during schema design. Project fields (Name, Stage, StartDate, EndDate, BudgetAmount) map directly. The Project's parent Organization (Account) lookup resolves via the Organization-to-Account ID mapping. BlueCamroo project templates export as structural metadata that we document separately for the customer's admin to use when building future projects in the custom Project__c schema.

BlueCamroo Tasks exist within Projects and across the CRM as standalone to-do items. We preserve subtasks by migrating parent and child Task relationships using Salesforce's WhatId pointing to the Project__c record for project-linked tasks and to the Account or Opportunity for standalone tasks. Priority, Status, and DueDate migrate directly. BlueCamroo checklist items within a Task map to Salesforce Task subtasks or a custom checklist field depending on complexity. Task assignment resolves OwnerId via the email-lookup User mapping.

BlueCamroo Time Entries log billable and unbillable hours against Projects with Date, Description, and Duration. We create a Time_Entry__c custom object with a lookup to Project__c (the parent project) and a lookup to the Contact (the resource who logged time). Billable flag migrates as a checkbox; hours and description migrate as Number and Text fields. The Project budget rollup requires a Salesforce Roll-Up Summary field on Project__c summing Time_Entry__c.Hours__c where Billable__c is true; this is configured during schema design.

BlueCamroo Products and Services map to Salesforce Product2 records. ProductCode migrates from the BlueCamroo SKU; Name and Description migrate directly. We create a Standard Pricebook entry for each Product2 during import. BlueCamroo's per-account price tiers map to Salesforce PricebookEntry records with different UnitPrice values per Pricebook2. If the customer uses multiple Price Books in BlueCamroo, each becomes a separate Salesforce Pricebook2.

BlueCamroo line items within Opportunities map to Salesforce OpportunityLineItem. We resolve the Pricebook2 reference, the Product2 reference, and the parent Opportunity at migration time. Quantity, UnitPrice, and TotalPrice migrate directly. BlueCamroo's discount-per-line-item field maps to Salesforce Discount field if present, or we store it in a custom field bc_discount__c.

BlueCamroo renamed Extra Data Objects to Custom Forms in version 8.3.10 (October 2022). Customers who created records before this release may have data in objects that only appear under the Extra Data Object label in the API. We query both the Extra Data Object and Custom Form API endpoints during discovery scoping to capture all containers. Each BlueCamroo custom data container becomes a Salesforce Custom Object with __c suffix. All custom fields (text, number, date, picklist, checkbox, lookup) are pre-created in Salesforce before migration using the Salesforce Metadata API or Change Set. Lookup relationships to standard objects (Account, Contact, Project__c) resolve via the ID mapping tables built during earlier phases.

BlueCamroo Invoices are generated from project costs, stage percentages, or fixed dates and include payment status and linked customer portal data. We map open invoices to a custom Invoice__c object with lookup to Account and Project__c, carrying invoice number, date, amount, and payment status. Closed invoices with full payment history map as Opportunity records with a Closed Won stage and Invoice__c as a child record for historical reference. Invoice PDFs are migrated as ContentDocument records attached to the Invoice__c or Opportunity. BlueCamroo's customer portal invoice visibility does not migrate; Salesforce Customer Portal or Experience Cloud is a separate configuration scope.

BlueCamroo's per-module subscription model assigns each user a role (CRM Only, Sales, Projects, Support, Complete) that determines feature access. We map BlueCamroo user roles to Salesforce Profiles (Standard User, Sales User, Support User) and Permission Sets that grant module-specific access. A BlueCamroo Complete user maps to a Salesforce Standard User profile; a BlueCamroo Sales-only user maps to a Sales User profile. Custom permission sets are created for any BlueCamroo-specific feature access that does not map directly to a standard Salesforce profile. The mapping is documented and handed off for the customer's admin to apply in production.