# Import First/Last Name Individually into Full Name Field

**URL:** <https://community.noloco.io/t/import-first-last-name-individually-into-full-name-field/694>\
**Category:** Feature Requests\
**Tags:** feature-request\
**Created:** [May 15, 2024, 5:19pm UTC](https://community.noloco.io/t/import-first-last-name-individually-into-full-name-field/694 "2024-05-15T17:19:48Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![fundmore](https://avatars.discourse-cdn.com/v4/letter/f/54ee81/32.png) [@fundmore](https://community.noloco.io/u/fundmore)\
**Post date:** [May 15, 2024, 5:19pm UTC](https://community.noloco.io/t/import-first-last-name-individually-into-full-name-field/694/1 "2024-05-15T17:19:48Z")

</div>

Right now you can only import a single string into a field of type _Full name_.

But often the data to be imported contains one column for first name, and another for last name.

It would be great if you could map both of these into the same _Full name_ field.

If you had multiple _Full name_ field named contact1 and contact2, the accepted column headers would be something like:

- contact1\_full
- contact1\_first
- contact1\_last
- contact2\_full
- contact2\_first
- contact2\_last

The obvious workaround is to have two text fields for first/last and a formula field combining them, but it’d be nice to be able to use Noloco’s auto-structured _Full name_ field.

---

<div class="post-metadata">

**Author:** ![darragh](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/darragh/32/12_2.png) [@darragh](https://community.noloco.io/u/darragh)\
**Post date:** [May 16, 2024, 5:28am UTC](https://community.noloco.io/t/import-first-last-name-individually-into-full-name-field/694/2 "2024-05-16T05:28:15Z")

</div>

Great suggestion @fundmore - we plan to support this type of functionality in imports really soon