Migrate from StreetSmart to Twenty CRM

StreetSmart People records map directly to Twenty CRM's People object. Every standard field (name, email, phone, job title) transfers as a direct column-to-column map. Records without a primary company link in StreetSmart land in Twenty as standalone People with no companyId — your team assigns them afterward.

StreetSmart lifecycle-stage values are stored as People-level custom fields. Twenty CRM has no native lifecycle-stage equivalent, so the field migrates as a custom select field (Lifecycle_Stage_raw) on the People object. Stage-transition timestamps preserve as Lifecycle_Stage_TS_raw custom datetime fields for reporting continuity.

StreetSmart Company records map 1:1 to Twenty CRM's Companies object. Company name, domain, industry, employee count, and annual revenue transfer as direct field maps. Parent-company hierarchies in StreetSmart map to Twenty's companyRelation one-to-many structure — child companies reference the parent via companyId.

StreetSmart deal records transfer to Twenty CRM Opportunities with deal name, amount, close date, and owner preserved directly. Stage names require a value-mapping step because Twenty Opportunity stages are defined per workspace as select pick-list values, not a global constant list.

StreetSmart deal stage values are mapped one-by-one to Twenty CRM's Opportunity stage select values. Each StreetSmart stage name becomes a corresponding Twenty stage label in the workspace stage configuration. Probability values and forecast-category assignments must be reapplied in Twenty after migration.

StreetSmart call and email engagement logs transfer as Twenty CRM Tasks. The Task.type field is set to 'Call' or 'Email' based on the source activity kind. Original timestamps and owner assignments are preserved so activity history on People and Opportunities reflects the full communication record from StreetSmart.

StreetSmart meeting records map to Twenty CRM Tasks with type set to 'Meeting'. Start and end times transfer to the task's due date window. Meeting titles map to the Task subject field. If StreetSmart stores meeting body content, it transfers as a Notes attachment linked to the task.

StreetSmart free-text notes and annotations migrate as Twenty CRM Notes objects. Notes are linked to their parent record (People, Companies, or Opportunities) via Twenty's relation model. Rich-text formatting is preserved in plain text for compatibility with Twenty's Note body field.

StreetSmart file attachments on records cannot be exported in a format that Twenty's CSV import accepts. We extract and archive the file manifest and, where StreetSmart provides a download URL, back up the files to a cloud storage location. Re-uploading files into Twenty's UI or via the API is a post-migration step your team or our team can complete.

StreetSmart custom objects migrate to Twenty CRM custom objects if your Twenty plan supports them (Pro tier: up to 10; Organization tier: unlimited). Custom object associations that use N:N relationships in StreetSmart must be surfaced in the migration plan — Twenty's relation model requires explicit junction objects for many-to-many relationships. Free and Starter plans cannot receive custom object migrations.

StreetSmart workflows, sequences, and automated triggers do not migrate to Twenty CRM. The automation logic must be rebuilt in Twenty's workflow builder from scratch. FlitStack AI can export your StreetSmart workflow definitions as a written reference document to give your Twenty admin a rebuild starting point, but the logic itself requires manual re-implementation.

StreetSmart owner IDs are resolved by email match against Twenty CRM Workspace Members. If a StreetSmart owner email matches a Twenty Workspace Member, records are assigned to that user. Unmatched owners are flagged before migration so your team can either invite them to Twenty first or assign their records to a fallback user.