Migrate from StrategicERP to Twenty CRM

StrategicERP stores client-facing contacts in its CRM module. These map directly to Twenty's People object. Each Person record in Twenty holds name, email, phone, job title, and a link to the parent Company via companyId. We extract contact records from StrategicERP's person entity and insert them in Twenty, resolving the companyId relationship by matching company names from the source.

StrategicERP's account or company entity maps one-to-one to Twenty's Companies object. Company name, domain or website URL, industry classification, employee count, and address fields transfer directly without transformation. Twenty's Companies object also supports a logo field, which we populate from StrategicERP's company logo reference when available in the source data.

StrategicERP deal or opportunity records map to Twenty's Opportunities. The deal name, amount, stage, expected close date, and owner all have direct field equivalents. StrategicERP pipeline stages map to Twenty's opportunity stage pick-list values. We apply a value-mapping table per stage name to preserve the probability and status logic from the source.

StrategicERP tasks linked to contacts or deals migrate to Twenty's Tasks object. Task subject, due date, completion status, and assignee (resolved by email) transfer directly. Tasks without a due date in the source land with no due date in Twenty. Orphaned tasks (unlinked) are flagged before migration for your team to reassociate.

StrategicERP notes attached to contacts, companies, or deals migrate to Twenty's Notes. Rich text content transfers as-is. Notes with attachments reference the files that we re-upload to Twenty's storage. The note's creation timestamp and author (resolved by email) are preserved as metadata on the Twenty record.

StrategicERP file attachments (documents, images, spreadsheets) associated with CRM records re-upload to Twenty and attach to the corresponding People, Company, or Opportunity record. We preserve the original filename and download URL. Inline images embedded in rich-text notes are extracted and rehosted as file attachments.

StrategicERP user IDs on records map to Twenty Workspace Members by email resolution. If a StrategicERP user email matches an existing Twenty Workspace Member, we assign OwnerId directly. Unmatched owners are flagged and assigned to a fallback Workspace Member you designate — no record lands without an owner.

StrategicERP custom fields on contacts, companies, and deals that have no direct Twenty equivalent are created as custom fields in Twenty before migration runs. We use Twenty's field type system (text, number, select, date, etc.) to match the source field type as closely as possible. You review the custom field list before we create them in your Twenty workspace.

StrategicERP custom objects that store CRM-relevant data (beyond standard contacts/deals) migrate to Twenty custom objects. Twenty supports unlimited custom objects at all tiers with N:1 relationships to standard objects. We map the custom object's fields to Twenty's schema and create the necessary relations. N:N relationships in StrategicERP require a junction object in Twenty.

StrategicERP's construction projects have a CRM dimension (project-linked deals, client关联) that cross-references the ERP project entity. We surface this as a custom text field on the Opportunity record in Twenty — your team decides whether to link it to a project management tool separately. This is preserved as a reference field, not an active link.

StrategicERP engagement records (logged calls, emails, meeting notes) migrate as Tasks in Twenty. Each activity record creates a Task with Type set to Call, Email, or Meeting, with the original timestamp and body content preserved. Complex activity threads may need splitting if the source stores them as a single nested record.

StrategicERP role-based permissions (project manager, estimator, accountant) do not map to Twenty's CRM-level permission model. We export the role structure as a reference document for you to rebuild manually in Twenty's settings. FlitStack AI does not migrate permissions — this is a destination-side configuration step.