Migrate your BlueCamroo data

BlueCamroo's primary account record is the 'shoebox' that holds all sub-records. Exported via Reports to CSV or directly via the REST API at api/account endpoints. We import these first, as every other object depends on a valid Organization ID.

Contacts live as sub-records under Organizations. The export template must include the Organization ID as a linking field. We sequence Contacts after Organizations in every migration to preserve the parent-child relationship.

Sales pipeline records linked to Organizations. BlueCamroo's Flex Services documents a dedicated import path for Sales Opportunities via database table insertion. We map pipeline stages to destination equivalents and preserve monetary values.

Support tickets linked to Organizations with status lifecycle (Open, In Progress, Closed, Re-Opened). Email-to-ticket routing is set via Workflow Rules that must be reactivated post-migration — we flag this during the cutover checklist.

Projects are full work records with Stages, Tasks, Time Entries, and budget tracking. BlueCamroo supports project templates which export as structural metadata. We preserve task dependencies and billable-hour flags but note that Task notifications are not re-created per BlueCamroo's own migration documentation.

Products and Services lists tied to Price Books with per-account pricing tiers. We import products as line items that feed Opportunities and Invoices. Multiple Price Books per account are supported and mapped 1:1.

Tasks exist within Projects and across the CRM as standalone to-do items. BlueCamroo supports subtasks, checklists, priority levels, and due dates. We preserve the parent-project linkage and assignees; standalone tasks are mapped to the destination equivalent (Tasks or Activities).

BlueCamroo renamed Extra Data Objects to Custom Forms in version 8.3.10 (2022). These hold custom sub-object data for leads, accounts, contacts, projects, and cases. Each Custom Object must be configured in the destination system before import; we insert via agreed intermediary format as documented in BlueCamroo's Flex Services.

BlueCamroo generates invoices from project costs, stage percentages, or fixed dates. Invoice records include payment status and linked customer portal data. We map open invoices and payment history but note that automated invoice reminder schedules must be reconfigured post-migration.

BlueCamroo Workflow Rules automate process steps and notifications across all modules. These are configuration records with conditional logic that cannot be exported as data — they must be manually rebuilt in the destination system. We document the active Workflow Rules during discovery and provide a rebuild checklist.

BlueCamroo's per-module subscription model means user roles determine which extensions a user can access. When migrating to a new platform, we map BlueCamroo user roles to the destination's permission model and flag which users had access to which modules to avoid license surprises.

Time logged against Projects with billable/unbillable flags and hour totals. We export time entry records via BlueCamroo's Reports or API and preserve the project linkage and owner assignment. Time entries feed into invoices and project cost tracking.