Migrate from BlueCamroo to Twenty CRM

BlueCamroo Organizations (the 'shoebox' container) map to Twenty CRM Companies. Organizations must export and import first because every other BlueCamroo record type (People, Opportunities, Cases, Projects) links to an Organization ID. We extract the BlueCamroo Organization IDs during export, then resolve the mapping to Twenty-generated Company IDs when importing child records. The BlueCamroo organization name, address, phone, website, and industry fields map to the corresponding Twenty Company fields.

BlueCamroo People records map to Twenty CRM Person records. The export must include the parent Organization ID as a linking field. We import People after Organizations are confirmed in Twenty, extract the BlueCamroo Person ID to Twenty Person ID lookup table, and apply that lookup when loading Opportunities, Cases, and Project assignments. Name, email, phone, title, and address fields migrate directly; any custom person-level fields map to Twenty custom fields configured during schema design.

BlueCamroo Opportunities map to Twenty CRM Opportunities. Opportunities are linked to Organizations and optionally to People. We resolve both the OrganizationId (to Company) and the primary ContactId (to Person) at migration time using the lookup tables built during the first two phases. Pipeline stages from BlueCamroo map to Twenty Opportunity stage values configured during schema setup, with probability percentages preserved.

BlueCamroo Cases map to Twenty CRM Opportunities with a 'Support' pipeline type, or to a custom Case object if the customer wants Case-specific status workflows. Cases link to Organizations and optionally to People. We preserve Case status lifecycle (Open, In Progress, Closed, Re-Opened), case owner assignment, and any linked email thread history. Email-to-ticket routing automations are Workflow Rules that do not migrate; we document them in the rebuild guide.

BlueCamroo Projects map to a Twenty CRM custom object named Project. Projects contain Stages, Tasks, Time Entries, and budget tracking. We create the Project custom object in Twenty during schema design, including custom fields for Stage, Budget, and Project Owner. Task dependencies and billable hour flags from BlueCamroo migrate to child Task records linked to the Project. BlueCamroo project templates export as structural metadata that we document as a setup guide for the customer's admin to re-create in Twenty.

BlueCamroo Products and Services lists map to Twenty CRM Products. Price Book entries with per-account pricing tiers migrate as custom fields or related records depending on the complexity of the tier structure. We import Products before Opportunities so that line items can reference the correct product records during Opportunity load.

BlueCamroo Tasks (standalone and within Projects) map to Twenty CRM Tasks. We preserve parent-project linkage via the Project custom object lookup, task assignees via Person or User resolution, due dates, priority levels, and subtask hierarchy. Note that BlueCamroo's own Flex Services documentation states Task notifications will not be re-created; we flag this gap and provide a rebuild checklist for post-migration notification reactivation.

BlueCamroo Time Entries linked to Projects migrate to a Twenty CRM TimeEntry custom object with fields for Hours, Billable flag, Date, Description, and Project lookup. We export billable/unbillable status and hour totals from BlueCamroo and map them to corresponding custom fields. Time Entry owners resolve to Twenty Person or User records at migration time.

BlueCamroo renamed Extra Data Objects to Custom Forms in version 8.3.10 (October 2022). We query both the Extra Data Object and Custom Forms API endpoints during discovery to capture all custom data containers regardless of which endpoint they live under. Each BlueCamroo custom object maps to a Twenty CRM custom object configured with equivalent fields. Lookup relationships from Extra Data Objects to Organizations, People, Opportunities, Projects, or Cases resolve to the corresponding Twenty IDs generated during earlier import phases.

BlueCamroo Invoices generated from project costs, stage percentages, or fixed dates map to a Twenty CRM Invoice custom object with fields for Invoice Number, Amount, Status, Date, and linked Organization (Company) and Project lookups. Open invoices and payment history migrate; paid invoices migrate with status preserved. BlueCamroo's customer portal data linked to invoices does not have a direct Twenty equivalent and is documented for admin awareness.

BlueCamroo's per-module subscription model assigns users to roles (Complete, Sales-only, Projects-only, Support-only) that determine feature access. Twenty CRM's permission model uses WorkspaceRole and field-level permissions. We map BlueCamroo user roles to Twenty WorkspaceRoles during migration, but full feature-access parity requires manual configuration in Twenty's workspace settings post-import because the permission models differ structurally.

BlueCamroo engagement records (calls, emails, meetings, notes) map to Twenty CRM Tasks (for calls and standalone tasks), Events (for meetings), and Comments (for note content attached to records). We preserve the activity timestamp, owner assignment, and parent record linkage (to Person, Company, or Opportunity). Email content migrates as a Task with the email body in a custom body field. Call duration and disposition migrate as custom Task fields.