CRM migration
Field-level mapping, validation, and rollback between Column Case Management and Twenty CRM. We move data and schema; workflows are rebuilt natively in Twenty CRM.
Column Case Management
Source
Twenty CRM
Destination
Compatibility
12 of 12
objects map 1:1 between Column Case Management and Twenty CRM.
Complexity
BStandard
Timeline
24–48 hours
Overview
Column Case Management is a purpose-built investigative case-management platform used by government agencies, law enforcement bureaus, and fraud-investigation teams. Its data model centers on Cases, Subjects, Evidence, Tasks, and Documents — organized around investigative workflows, solvability scoring, and role-based case access. Twenty CRM is an open-source sales-oriented CRM with standard objects for People, Companies, Opportunities, Tasks, and Notes, plus unlimited custom objects. The migration requires transforming Column's investigative-case schema into Twenty's People/Company/Opportunity model — the most substantial structural divergence in our catalog. We map Column Cases to Twenty Opportunities (repurposed as a 'Case' custom object if the Opportunity label is misleading), Column Subjects to Twenty People, and Column Organizations to Twenty Companies. Evidence records and case attachments migrate as Twenty Notes and Files. Column's investigator and group assignments become Twenty Workspace Members, resolved by email match. Workflows, triggers, and integration connectors (BMC Remedy, AR Framework hooks) do not migrate — we export their definitions for your Twenty admin to rebuild using Twenty's workflow builder. The migration uses Twenty's REST and GraphQL APIs, respecting its rate limits of 100 requests per minute on the free tier and 200 on Organization cloud, with CSV import as a secondary path for large record sets.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Column Case Management object lands in Twenty CRM, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Column Case Management
Case
Twenty CRM
Opportunity (Case custom fields)
1:1Column Cases map to Twenty Opportunities with a suite of custom fields: Case_Type__c, Investigative_Status__c, Solvability_Score__c, and Case_Priority__c. The case title becomes Opportunity Name, case create date becomes a custom Created_Date__c field since Twenty's standard CreatedDate is set at import time. Case status values (Open, In Progress, Closed, etc.) are mapped via value_mapping to Twenty custom pick-list options.
Column Case Management
Case Assignment
Twenty CRM
Opportunity Assignee (Workspace Member relation)
1:1Column Case assignments (investigator ID and group ID) resolve against Twenty Workspace Members by email match. Unmatched investigators are flagged before migration. Multiple-case assignments per investigator are preserved by linking the investigator's email as a custom field on each Opportunity record in Twenty.
Column Case Management
Subject
Twenty CRM
People
1:1Column Subjects — the individuals being investigated — map directly to Twenty People. Standard fields (first name, last name, email, phone, job title, address) transfer as direct mappings. The Column Subject_ID is stored as a custom Source_System_ID__c field on the Twenty People record for traceability and delta-run de-duplication.
Column Case Management
Subject Type
Twenty CRM
People (Custom Select field: Subject_Type__c)
1:1Column CCM subject types (Witness, Suspect, Victim, etc.) have no direct equivalent in Twenty's standard People fields. We create a custom select field Subject_Type__c on the People object with the exact pick-list values from Column CCM, preserving the investigative role label on each People record.
Column Case Management
Organization (Column CCM company record)
Twenty CRM
Companies
1:1Column Organizations — the companies or agencies associated with cases — map directly to Twenty Companies. Fields including name, domain/website, industry, employee count, and address transfer as direct mappings. Column Organization_ID is preserved as Source_System_ID__c for reference and delta-run matching.
Column Case Management
Evidence Record
Twenty CRM
Notes + Files (or Custom Object)
1:1Column Evidence records (description, evidence type, chain-of-custody notes, file attachments) are split: the descriptive and textual data migrates to Twenty Notes attached to the relevant Case-Opportunity. File attachments are re-uploaded to Twenty Files and linked to the same Opportunity. Teams requiring full evidence-chain metadata create a custom Evidence custom object in Twenty, with fields for evidence type, custody notes, and a File relation.
Column Case Management
Task / Action Item
Twenty CRM
Tasks
1:1Column Tasks associated with cases (follow-up actions, evidence collection steps, interview scheduling) map directly to Twenty Tasks. Task title becomes the Task name, description maps to the body, status values map via value_mapping to Twenty Task status (To Do, In Progress, Completed), and the assigned investigator resolves by email match to a Twenty Workspace Member.
Column Case Management
Document
Twenty CRM
Notes + Files
1:1Column Documents (case files, reports, correspondence) migrate as Twenty Notes with file attachments. The document title becomes the Note subject. For documents without a note body, we create a minimal Note record in Twenty and attach the file. All documents inherit the same Opportunity (Case) parent linkage as the case they belong to.
Column Case Management
User / Investigator
Twenty CRM
Workspace Members
1:1Column Users and Investigators resolve against Twenty Workspace Members by email. Active Column users without a matching email are flagged as unmapped before migration — your team either creates Twenty accounts for them first or assigns their records to a fallback Workspace Member. Role and permission sets from Column CCM (Admin, Investigator, Viewer) cannot transfer directly and must be reconfigured in Twenty's permission settings.
Column Case Management
Group / Unit
Twenty CRM
Twenty Workspace (no direct equivalent)
1:1Column CCM organizational Groups and Units have no direct equivalent in Twenty CRM. Group-based case assignments are resolved at the individual investigator level by email match. If your team relies on group-level permissions and reporting in Column, that structure must be rebuilt in Twenty using Workspace-level Views and filtering.
Column Case Management
Integration: BMC Remedy / AR Framework
Twenty CRM
No equivalent
1:1Column CCM integrations with BMC Remedy (auto-case creation from incidents) and the AR Framework do not have equivalents in Twenty CRM. These connections must be rebuilt from scratch — either using Twenty's REST API to push incident data or using a middleware tool like Zapier or Make to trigger Opportunity creation in Twenty when an incident is created in Remedy.
Column Case Management
Attachment / File
Twenty CRM
Files (Twenty CRM native)
1:1Column file attachments — documents, evidence files, images — are re-uploaded to Twenty Files and linked to the parent record (Opportunity or People). Twenty's file size limits apply. We re-download inline images from notes, rehost them in Twenty's file storage, and update the linked Note with the new file reference.
| Column Case Management | Twenty CRM | Compatibility | |
|---|---|---|---|
| Case | Opportunity (Case custom fields)1:1 | Fully supported | |
| Case Assignment | Opportunity Assignee (Workspace Member relation)1:1 | Fully supported | |
| Subject | People1:1 | Fully supported | |
| Subject Type | People (Custom Select field: Subject_Type__c)1:1 | Fully supported | |
| Organization (Column CCM company record) | Companies1:1 | Fully supported | |
| Evidence Record | Notes + Files (or Custom Object)1:1 | Fully supported | |
| Task / Action Item | Tasks1:1 | Fully supported | |
| Document | Notes + Files1:1 | Fully supported | |
| User / Investigator | Workspace Members1:1 | Fully supported | |
| Group / Unit | Twenty Workspace (no direct equivalent)1:1 | Fully supported | |
| Integration: BMC Remedy / AR Framework | No equivalent1:1 | Fully supported | |
| Attachment / File | Files (Twenty CRM native)1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Column Case Management gotchas
Float/Concurrent license scoping affects migration user mapping
Customization re-application required on major version upgrades
No publicly documented REST API with published rate limits
BMC/Remedy integration creates auto-generated Cases that may duplicate manually entered records
Twenty CRM gotchas
Import order is enforced and critical
Export limited to 20,000 records and visible columns only
Soft-deleted records count toward uniqueness and trigger restores
API rate limits cap at 200 req/min on Organization tier
No native email sequences — follow-up cadences require external tools
Pair-specific challenges
Migration approach
Audit Column CCM data export and schema
We connect to Column CCM's API (or work with CSV exports from your reporting interface) and pull a complete data inventory: all Cases, Subjects, Organizations, Evidence records, Tasks, Notes, Documents, and User accounts. We audit field completeness, duplicate rates, and relationship integrity. We also document your Column CCM workflows, triggers, and integration connections (BMC Remedy, AR Framework) so we can export their definitions for your Twenty admin to rebuild. This phase produces the migration specification document — your sign-off before any data moves.
Set up Twenty CRM workspace and custom schema
Before data lands, we create all required custom fields in Twenty: Case_ID__c, Case_Type__c, Solvability_Score__c, Case_Status__c, Investigative_Type__c, Case_Origin__c, Subject_Type__c, Evidence_Type__c, Custody_Notes__c, and Source_System_ID__c on relevant objects. If you prefer a dedicated Case object, we create that as a Twenty custom object with the same fields. We invite all team members to Twenty and match their email addresses against Column CCM investigator and user records. Your admin reviews the custom field setup in Twenty Settings before we proceed to migration.
Run sample migration with field-level diff
A representative slice migrates first — typically 100–300 records spanning a few Cases, their linked Subjects, Evidence records, Tasks, and Notes. We generate a field-level diff between the Column CCM source values and the migrated Twenty records so you can verify that case status mapping, investigator assignment, solvability score preservation, and evidence-chain linkage all landed correctly. We surface any mapping corrections before the full run commits. This sample run typically completes in 2–4 hours.
Execute full migration with delta-pickup window
The full data set migrates in sequenced order respecting Twenty's API rate limits and the dependency order (Organizations first, then People, then Opportunities, then Tasks/Notes). A delta-pickup window — typically 24–48 hours — captures any records created or modified in Column CCM during the cutover window. All operations are logged in an audit trail, and one-click rollback is available if reconciliation fails. Your team keeps working in Column CCM throughout the migration window.
Export workflow definitions for Twenty rebuild
FlitStack AI exports your Column CCM workflow definitions, trigger logic, and automation rules as structured documentation — including trigger conditions, action sequences, and notification routing. This document serves as the rebuild reference for your Twenty admin. We do not migrate automations directly (they are not data), but we give your team the specification they need to reconstruct investigative workflows using Twenty's workflow builder. Integration connections (BMC Remedy, AR Framework hooks) are documented separately for your technical team to implement via Twenty's REST API or webhook endpoints.
Validate migrated records and final reconciliation
We run record-count reconciliation across all object types, spot-check field values against the source data, and verify that all file attachments landed in Twenty Files and are linked to the correct parent records. Investigator assignments are verified by sampling 20+ records and comparing the assigned user in Twenty against the Column CCM investigator. We deliver a final migration report with record counts, any unmapped records, and the action items for your Twenty admin to complete post-migration setup.
Platform deep dives
Column Case Management
Source
Strengths
Weaknesses
Twenty CRM
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Column Case Management and Twenty CRM.
Object compatibility
2 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Column Case Management: Not publicly documented.
Data volume sensitivity
Column Case Management doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Column Case Management to Twenty CRM migration scoping. Not seeing yours? Book a call.
Walk through your Column Case Management to Twenty CRM migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Column Case Management
Other ways to arrive at Twenty CRM
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.