Migrate from Constructor to Twenty CRM

Constructor contacts migrate as Twenty People records. First name, last name, email, phone, job title, and address fields map directly. The People object links to Companies via the companyId field — Constructor contacts without a primary company receive a 'Unassigned' placeholder or remain standalone until a company link is established during the Companies import phase.

Constructor accounts map to Twenty Companies. The Companies object in Twenty stores displayName, domain (website), industry, size, and location fields. Constructor parent-child account hierarchies translate to Twenty's company-to-company relationships via a parentCompanyId field if your Constructor setup uses organizational hierarchies.

Constructor deals migrate as Twenty Opportunities with the same deal name, amount, stage, and expected close date. Twenty Opportunities link to Companies (accountId) and can link to People (point of contact). Stage names map value-by-value if Constructor uses a pick-list for stages — we preserve the original stage labels as Opportunity stage values in Twenty.

Constructor notes attach to contacts, companies, or deals. In Twenty, Notes are standalone objects that link to People, Companies, Opportunities, or other records via the NoteTargets relation. We preserve the original note body, author, and create timestamp. Rich-text formatting converts to Twenty's supported note format.

Constructor tasks migrate as Twenty Tasks with the task title, due date, assignee, completion status, and body preserved. Tasks link to the parent record (People, Company, or Opportunity) via taskId. Completed versus open status carries over as a boolean completed field in Twenty.

Constructor activity logs (call logs, email threads, meeting records) split based on type. Call and email activities become Tasks with Type='Call' or Type='Email' in Twenty. Meeting records with start/end times convert to Twenty Tasks with a scheduled datetime if Twenty's event model is not available in your version. Original activity timestamps and owners (resolved by email) are preserved.

Constructor custom objects migrate 1:1 to Twenty custom objects. Your Twenty workspace must have the custom object schema created (via Settings → Data Model → Create new object) before migration runs. We export the custom object definition from Constructor and use Twenty's Metadata API to create matching objects with the same field types — text, number, date, select, multi-select, or relation.

Constructor custom fields on contacts, accounts, or deals require pre-creation in Twenty's data model before CSV import. We document all custom fields in the mapping plan, flag which Twenty object each custom field belongs to, and include the field type from Constructor. Your admin creates these in Settings → Data Model first — FlitStack cannot create fields, only data.

Constructor users and deal owners resolve by email match against Twenty workspace members. The Twenty import documentation explicitly requires that users exist before importing records that reference them — we flag unmatched owners before migration and either invite them to Twenty first or assign their records to a fallback workspace member.

Constructor file attachments on contacts, companies, or deals export from Constructor's storage and re-upload to Twenty's file storage. We preserve the original file name, mime type, and upload timestamp. Files attach to the parent record in Twenty using the file associations API. Size limits from Constructor's export apply.

Constructor workflows and automation rules do not migrate to Twenty. Twenty's workflow builder operates differently from Constructor's automation engine. We export your Constructor workflow definitions as a JSON reference file so your Twenty admin can rebuild them in Settings → Workflows. This is a manual step that requires process review.

Constructor sequences and outreach cadences do not transfer. Reddit discussions about Twenty note that it 'lacks native sequencing' as of v1.0. Sequences must be rebuilt manually in Twenty or via a third-party sales engagement tool. We export sequence definitions as reference documentation.