Migrate from Followup CRM to Twenty CRM

Followup CRM contacts migrate directly to Twenty People records. The primary company association uses Twenty's companyId foreign key, which requires the referenced Company to be imported first. Contacts without a primary company land in Twenty as standalone People records with no companyId.

Followup CRM companies map 1:1 to Twenty Companies. Domain-based linking in Followup CRM (for website matching) translates to Twenty's domain unique field for deduplication. Parent-child company hierarchies use Twenty's relation field if supported, or are flattened if the relationship is not expressible.

Followup CRM's Projects are the primary deal-tracking entity in a construction-sales context. They migrate to Twenty Opportunities with project-level fields (bid volume, goals, milestones) mapped to custom fields on the Opportunity record. The follow-up task chain associated with each Project migrates as individual Tasks linked to the Opportunity.

Followup CRM User-type custom fields store a reference to another Followup CRM user (e.g., assigned estimator). These migrate as Twenty relation fields pointing to the WorkspaceMember object, resolved by email match — the Twenty user must exist in the workspace before the relation can resolve.

Followup CRM Dropdown custom fields carry a defined list of options with description and load order. Each option migrates as a select or multi-select value in Twenty's corresponding custom field. The option order is preserved from Followup's load order values.

Followup CRM Text-type custom fields migrate directly to Twenty text-type custom fields without any transformation. Both the field display names and the underlying string data type carry over exactly as they appear in Followup CRM, preserving any labels, descriptions, or placeholder text associated with each field during the migration.

Followup CRM follow-up items (reminders, task sequences tied to projects) map to Twenty Tasks. The original due date, assignee (via User field → WorkspaceMember relation), and completion status are preserved. Open follow-ups migrate as open Tasks; completed ones carry their completed timestamp.

Followup CRM team goal-setting and quota configuration—including bid volume targets, revenue goals, and per-user allocations—has no equivalent object in Twenty's current data model. These cannot be migrated as data records. FlitStack AI exports the full goal and quota definitions (targets, assignments, and thresholds) as a structured reference document so administrators can reconstruct the equivalent reporting setup using Twenty's custom fields and reporting tools.

Followup CRM automation sequences—including automated follow-up triggers, stage-transition logic, and action-based rules—do not migrate because they are configuration rather than data records. FlitStack AI exports the complete sequence definitions, documenting each step's trigger conditions, actions, and stage transitions in a structured format that serves as a detailed rebuild checklist for Twenty's workflow builder.

Files attached to Followup CRM contacts, companies, or projects are downloaded from the source system and re-uploaded to Twenty's native file storage. For self-hosted deployments, files may alternatively be linked externally if the storage architecture supports it. File size limits apply on Twenty Cloud (as defined by your tier), while self-hosted deployments inherit whatever storage constraints the hosting server defines.

Followup CRM users (Owner, Admin, Regular) resolve to Twenty WorkspaceMembers by email address match. Unmatched owners are flagged before migration — either invited to Twenty first or assigned to a fallback WorkspaceMember. Owner-level permissions in Followup CRM (for custom field creation) do not map to any Twenty permission tier.