Migrate from ServeCircle to Twenty CRM

ServeCircle has no production API — migration relies on CSV exports and direct database reads

ServeCircle's Advanced and Enterprise tiers label the Web API as 'Coming soon', which means there is no authenticated REST endpoint to pull data programmatically. FlitStack AI must extract data either through CSV exports from the ServeCircle UI (limited to what the export function exposes per object) or through direct reads of the ServeCircle database if credentials are provided. CSV exports are scoped to the current view's visible columns, so all required fields must be present in the exported view before export runs. If ServeCircle database access is unavailable, any fields not exposed in the CSV export are flagged as no_equivalent and preserved as best-effort text notes attached to the relevant record in Twenty. This is the single largest risk factor in a ServeCircle migration — it is not a technical limitation of FlitStack but a platform constraint of the source system.

Twenty imports require correct dependency order — companies before people before opportunities

Twenty's CSV import function enforces referential integrity: related records must exist before they can be referenced. Specifically, Companies must be imported first (as the 'one' side of the one-to-many relationship), followed by People (which reference a companyId), followed by Opportunities (which reference both a companyId and a personId). If this order is violated, import rows with unresolvable foreign keys are rejected and flagged in the error log. ServeCircle's data does not expose foreign key IDs in CSV exports — we must reconstruct relationships from email domain matching (for companyId on People) and from job-sheet client references (for personId on Opportunities). This reconstruction step adds 1–2 days to the planning phase and must be validated in the sample migration before the full run commits.

ServeCircle service-type and inventory data requires custom objects not present in Twenty's standard schema

ServeCircle service categories (Basic, Advanced, Enterprise tiers) and inventory items (spare parts, consumables) are first-class data objects in ServeCircle but have no equivalent in Twenty's standard data model. Twenty's standard objects are People, Companies, Opportunities, Notes, and Tasks. Migrating service types and inventory items requires creating custom objects in Twenty before the migration import runs — ServiceType and InventoryItem objects must be created in Settings → Data Model, and all custom fields (SKU, quantity, reorder level, unit cost for inventory; service name, estimated duration, base price for service types) must be added before CSV rows referencing those objects are loaded. Failure to pre-create these objects results in import errors on all related records. FlitStack delivers a schema-setup checklist as part of the migration plan so these objects exist before data lands.

ServeCircle multi-branch technician assignments do not map natively to Twenty's Workspace Member model

ServeCircle supports unlimited branches and users across branches with per-branch service management. A technician in ServeCircle may be assigned to jobs across multiple branches. Twenty's Workspace Members are workspace-level (not branch-level), meaning a technician can be assigned to any Opportunity regardless of branch, but there is no native branch-membership concept on the member record. We preserve branch assignments as a custom multi-select field (assigned_branches__c) on the Workspace Member record. Branch-level data isolation (so technicians see only their branch's jobs) would require Twenty workspace isolation, which is an architectural decision your team should evaluate before migration — it is not handled automatically by the data migration.

ServeCircle workflow definitions and SMS/email alert configurations cannot migrate to Twenty

ServeCircle's Advanced and Enterprise tiers include workflow rules, SMS/email alert triggers, quotation approval chains, and signature capture flows. Twenty's workflow builder is its own automation engine with different trigger conditions, action types, and evaluation logic. No automated conversion path exists between ServeCircle workflows and Twenty workflows. FlitStack AI exports ServeCircle workflow definitions as a structured reference document (JSON) listing each workflow's trigger event, conditions, and actions so your Twenty admin can rebuild them. SMS and email alert templates (which ServeCircle sends on job registration, work completion, and delivery) have no Twenty equivalent — these must be rebuilt using Twenty's workflow builder or a third-party email/SMS integration. The rebuild effort should be scoped as a separate workstream from the data migration.