Object to Object Conversion (eg Lead to Opportunity)

[oddieis]

Scope & Context

I would like to request enhanced object management in Twenty CRM.
The ticket is about enabling users to convert leads directly into any custom object of their choosing, instead of manually copying data.

Current behavior

Currently, when a lead is received and stored as a custom object, it cannot be directly converted into another object like an opportunity.
This forces users to manually transfer data from the lead to the desired object type, which is inefficient and error-prone.

Expected behavior

Users should be able to select a lead and convert it directly into a custom object of their choice.
The system should automatically map and transfer the data from the lead into the custom object format.

Technical inputs

• Extend the lead model to include metadata for custom object mapping.
• Create a conversion API endpoint that accepts the target custom object type and performs the necessary data transformation.
• Implement a modal dialog in the UI for users to select the custom object type and preview the mapping before conversion.
• Ensure robust error handling and rollback mechanisms in case the conversion process fails.

[FelixMalfait]

Hey, I'm sorry I'm not sure I understand. Do you mean (Lead -> People + Company) type of conversion like in Salesforce? (which would be a custom -> standard object conversion since we don't have a Lead object today).
Or is that for the data model to automatically adapt when you do a CSV import?
Or something else?

[oddieis]

Essentially yes it is an object to object conversion, like in salesforce. Allow each system to define mappings for object to object conversion. The idea is that a lead needs to be converted into 1 or more objects to be used after initial review.

This will solve for lead (custom object) conversion as well as other object conversion scenarios.

The exact destination object converted into will change depending on the user's selected crm implementation. So the request is for the ability to define 1 or more template conversion mappings between a source and a destination object(s).

This would mean essentially creating a 'conversion template' which says:

1. when I press 'convert' button on the object A, eg lead custom object, it triggers a modal box.
2. That box allows me to select a particular template that was predefined in the settings area
3. In each template, the lead (custom object) converts into something fixed, eg 'selected lead fields a, b, and c convert to objects account, contact and opportunity', or 'lead fields convert into 'custom opportunity object' etc. Fields on each destination object are also defined within this mapping.

The idea is that a conversion should not pay attention to whether the destination is a standard or a custom object. It simply allows a template to define source and destination.