Migrate from ServeManager to Twenty CRM

ServeManager Company maps 1:1 to Twenty Companies. The domain field in ServeManager maps to Twenty's domain field, enabling automatic company-to-people linking by domain during import. If the source company record has a parent/branch structure, the hierarchy maps using Twenty's Relation field pointing to the parent Company record.

ServeManager stores client contacts (law firms, attorneys, agencies) as a separate entity linked to Jobs. These map to Twenty People. The email field on the contact resolves the person-to-company relation in Twenty using domain-matching or the companyId reference from ServeManager's export.

ServeManager Job is the core work unit — it maps to Twenty Opportunity. The job name becomes the Opportunity name. Job status (Pending, In Progress, Served, etc.) maps to Twenty Opportunity stage values via a value-mapping table. The due date from the job migrates as the Opportunity expectedCloseDate. The ServeManager Job ID is stored as Source_System_ID__c on the Twenty Opportunity for traceability.

Each service attempt on a ServeManager Job maps to a Twenty Task linked to the corresponding Opportunity record. GPS latitude and longitude from ServeManager attempt records migrate as custom number fields (Attempt_Latitude__c, Attempt_Longitude__c) on the Twenty Task. The attempt timestamp migrates as the Task due date and as a custom Attempt_Timestamp__c field. Electronic signature status and photo proof links migrate as custom text fields pointing to the file URL.

ServeManager Invoice records carry billing amount, status, and Stripe payment reference. Twenty has no native invoice object, so we attach invoice data as a rich-text Note on the related Opportunity. Invoice amount and status are also stored as custom fields (Invoice_Amount__c, Invoice_Status__c) on the Opportunity for reporting use.

ServeManager Payment records track what was actually collected against an invoice. Since Twenty lacks a payment object, payment data migrates as custom fields on the Opportunity: Payment_Date__c, Payment_Method__c, and Payment_Reference__c. The Stripe charge ID from ServeManager is preserved in Payment_Reference__c for reconciliation.

ServeManager tracks process servers (agents) who perform the service. These map to Twenty Workspace Members by email match. ServeManager's server contact info (name, phone, email) migrates as the Workspace Member profile. Unmatched servers are flagged before migration and can be invited to Twenty before the final run.

ServeManager allows categorizing jobs by service type (e.g., Eviction, Subpoena, Summons, TPOA, Notice). Twenty does not have a native service-type field on the Opportunity object, so we create a custom select field (Service_Type__c) with pick-list values that match the source ServeManager categories exactly. This preserves your existing categorization workflow and allows filtering and reporting by service type in Twenty after migration is complete.

ServeManager supports custom fields on Jobs beyond the standard fields. Each custom field on a ServeManager Job requires a corresponding custom field in Twenty Settings → Data Model before import. FlitStack generates the field creation plan during scoping and delivers it as a pre-migration setup checklist.

ServeManager stores document attachments (affidavits, proof of service PDFs) linked to Jobs. Files migrate by re-uploading to Twenty's file storage and attaching as Notes with the original filename and a link to the uploaded file. File size limits on the destination apply — documents over 25MB are flagged for chunking.

ServeManager captures GPS coordinates and timestamps for every attempt. These do not map to a native Twenty field. We create Attempt_Latitude__c and Attempt_Longitude__c as custom number fields on the Task object. The original GPS accuracy reading from ServeManager migrates as Attempt_GPS_Accuracy__c for audit purposes.

ServeManager lets clients log in to a portal to view job status and upload documents. This portal access is a ServeManager billing feature with no direct Twenty equivalent. We preserve the client portal access status as Client_Portal_Access__c on the Person record as a reference flag for manual re-enrollment if needed.