Migrate from BlueCamroo to Nutshell

BlueCamroo Organizations are the parent container for all sub-records and export as the first phase of every migration. We map Organization name to Company name, Organization address fields to Nutshell Company address fields, and use Organization ID as the dedupe key during import. This is the foundational record that every other import phase references — it must land before any Contact, Opportunity, or Case import.

BlueCamroo Contacts attach under Organizations and export with an Organization ID linking field. We map the linking field to the newly created Nutshell Company ID using the lookup table built during the Organizations phase. Person name, email, phone, title, and custom fields migrate directly. If the BlueCamroo Contact has no Organization (a rare edge case in BlueCamroo but possible with direct API inserts), we create a stub Company record first.

BlueCamroo Opportunities link to Organizations and include pipeline stage, estimated value, and close date. We map Opportunity name to Nutshell Deal name, estimated value to monetary fields, close date to close date, and pipeline stage to Nutshell stage values. BlueCamroo pipeline stages are mapped to Nutshell's default stage set (Prospecting through Closed Won/Lost), with any custom stages mapped as closely as the destination allows.

BlueCamroo Cases link to Organizations with a status lifecycle (Open, In Progress, Closed, Re-Opened) and conversation history. Nutshell does not have a native Cases module, so we map Cases to a custom Nutshell object or to Deals with a Case type flag. Email-to-case routing is set via BlueCamroo Workflow Rules that do not migrate — we document the routing logic in the Workflow inventory for the customer's admin to rebuild using Nutshell's automation rules or a connected helpdesk app.

BlueCamroo Products and Price Books with per-account pricing tiers migrate to Nutshell Product records. Product name, SKU, and unit price map directly. BlueCamroo price book tiers are preserved as custom fields on the Product record since Nutshell does not have a native Price Book multi-tier structure.

BlueCamroo Projects include stages, tasks, time entries, billable hours, and budget tracking — none of which have native Nutshell equivalents. We decompose Projects into a Deal record (for project name, stage, and estimated value) plus custom fields on the linked Company or Deal to carry project metadata (budget, hours logged, project template origin). Time entries migrate as line-item custom fields on the Deal. For customers with complex project dependencies, we recommend a dedicated project management migration to a tool like Asana or monday.com as a separate engagement.

BlueCamroo renamed Extra Data Objects to Custom Forms in version 8.3.10 (October 2022). We query both API endpoints during discovery to ensure no custom object is missed. Each Extra Data Object or Custom Form maps to Nutshell custom fields on the appropriate base object (Company, Person, or Deal) configured before import. Multi-value custom fields map to Nutshell multi-select fields where supported.

BlueCamroo time entries are logged against Projects with billable/unbillable flags, owner assignment, and hours totals. Since Nutshell has no native time tracking, we aggregate time entry totals by Project and attach them as custom numeric fields on the related Deal or Company record. Itemized time entry records with individual dates and descriptions are preserved in a CSV export delivered alongside the migration for reference or integration with a time-tracking tool.

BlueCamroo's per-module subscription model assigns users to role types (CRM-only, Sales, Projects, Support, Complete). We map BlueCamroo role types to Nutshell User accounts by email match. Any BlueCamroo user without a matching Nutshell account goes to a reconciliation queue for the customer to provision before the final record import phase.

BlueCamroo Workflow Rules automate process steps across CRM, Sales, Projects, and Support modules. These are configuration records with conditional logic that cannot be exported via the API or Reports. We document every active Workflow Rule during discovery (trigger type, conditions, actions, and associated object) and deliver a written rebuild guide mapped to Nutshell's automation rules. The customer's admin recreates these post-migration.