Migrate from Service In Sync to Twenty CRM

Service In Sync contacts migrate as Twenty People records. Each contact's primary company resolves to a Twenty Company via domain match or explicit companyId field. Owner is resolved by email match against Twenty workspace members — unmatched owners are flagged for manual assignment before the full migration runs.

Service In Sync companies map directly to Twenty Companies. Parent-child company hierarchies in Service In Sync map to Twenty's Parent Company relation field if present. Multi-contact companies in Service In Sync maintain their People links via companyId on each Person record after migration.

Service In Sync jobs carry a richer structure than a standard deal — they include scheduling dates, crew assignments, approval statuses, line items, and client sign-off data. FlitStack AI maps the job amount and stage to Twenty Opportunity fields, and stores scheduling metadata (scheduled date, assigned crew) as custom fields on the Opportunity record.

Service In Sync job statuses (e.g., Request, Scheduled, In Progress, Completed, Invoiced, Cancelled) map to Twenty Opportunity stage values via value-by-value mapping. Each stage name from Service In Sync gets a corresponding Twenty stage pick-list value defined in the migration plan before import.

Service In Sync custom fields on contacts (beyond standard name/email/phone) require custom fields in Twenty's Settings → Data Model. FlitStack AI creates the corresponding Twenty custom fields before import and maps values field-by-field. Field type is inferred from Service In Sync data (text, number, date, select).

Service In Sync custom fields on jobs — such as service type, crew size, equipment used, or client-specific metadata — are recreated as custom fields on Twenty Opportunities. Scheduling-derived fields (e.g., crew assignment data) are preserved as text or relation fields depending on their structure.

Service In Sync engagement logs — notes, follow-ups, client communications tied to jobs — migrate as Twenty Tasks. Each Task links to the parent People or Opportunity record via the relation field. Original timestamps and assigned user (resolved by email) are preserved.

Service In Sync notes on contacts, companies, or jobs migrate as Twenty Notes. Rich-text formatting is preserved where possible. File attachments from Service In Sync are flagged for manual re-upload — Twenty does not natively store attachments on records, so these require post-migration handling via Twenty Files or an external storage integration.

Service In Sync users and job owners are matched to Twenty workspace members by email address. Unmatched owners are flagged before migration with a recommendation to invite them to the Twenty workspace first. Once matched, all records receive the correct OwnerId without orphaned assignments.

Service In Sync custom objects (Enterprise tier) map to Twenty custom objects on the Pro or Organization tier. The target custom object must be pre-created in Twenty Settings → Data Model. Relations between custom objects and standard objects (People, Companies, Opportunities) use Twenty's relation field type and are established after the primary objects are migrated.

Service In Sync automations (job reminders, approval routing, follow-up triggers) do not migrate. FlitStack AI exports your automation definitions as a structured rebuild reference so your Twenty admin can recreate equivalent logic in Twenty's workflow builder. This is a manual step — automation rebuild is scoped separately from data migration.

Service In Sync's review-booster feature — which directs post-job customers to leave reviews on Google, Yelp, or Facebook — has no equivalent in Twenty CRM. Review history and review request records are preserved as reference notes, but the active review-automation logic must be rebuilt using a third-party reputation tool post-migration.