Twenty gives teams a configurable CRM that can be self-hosted. Its records, pipelines, and workflows can remain the relationship reference while Uranus holds selected dated evidence and reviewed portfolio work. Self-hosting does not make the existing configuration disposable; it can make preserving that investment even more important.

Twenty’s documented CSV view export depends on visible fields and filters. It has record-count and attachment limitations, and relation identifiers need careful handling. Bring companies before dependent people and retain stable IDs, so importing a person does not silently create the wrong company connection. An API route should use the actual workspace-generated schema and a restricted role.

The product’s open-source license also matters. Twenty core is not a blanket permissive foundation for copying into a separately licensed application; the exact license and enterprise boundary must be reviewed. This build uses workflow inspiration and API/export research, with its own implementation. Uranus currently provides a Twenty guide and generic mapping, without a native Twenty connector. The proposed benefit is a VC-specific path from evidence to decision conditions, assigned work, and reviewed outcomes. It should be measured against what the firm can already configure in Twenty.

A first import you can review

  • Create an export view with IDs and needed fields visible; choose filters deliberately.
  • Use Export view CSV for each object. Export the many-side relation IDs and bring companies before dependent people.
  • For larger datasets use authorized schema-generated APIs; review in a staging import before committing.

What Uranus adds today

Review the mapping, units, currency, and reporting month before committing. New metrics remain candidates until a workspace owner reviews them. Preserve originals and source identifiers, keep the requested next evidence visible, and attach a reviewed resolution when the work is complete. Export canonical records and version history when you need to move the work again.

This is a proposed workflow based on public documentation, not a paid-account benchmark or a demonstrated performance improvement. Verify the actual entitlement, export schema, and effective permissions with the firm’s administrator. Native formats require customer fixtures before claiming automatic compatibility.