Currently, when attempting to import CSV data into a Confluence database, any column intended to link to another database entry gets converted into a smart link, rather than being recognized as an "Entry link" field type. This results in the imported field showing a link card to the other database rather than dynamically linking and displaying the referenced entry's specific field value.

Use Case:
Teams migrating from external systems often need to preserve relational links between datasets—especially when importing large volumes of structured information across multiple databases. Manual linking post-import is time-consuming and not scalable.

Request:

• Enhance the CSV import process to allow recognition of "Entry link" field type if the format matches a valid database entry URL or identifier.

• Allow bulk automation of database relationships through import.

• Improve field type detection logic for cases where the target is clearly a database entry.