# Bulk Modbus Tags Adding

**URL:** <https://forum.inductiveautomation.com/t/bulk-modbus-tags-adding/110475>\
**Category:** Ignition\
**Tags:** modbus\
**Created:** [September 9, 2025, 6:49am UTC](https://forum.inductiveautomation.com/t/bulk-modbus-tags-adding/110475 "2025-09-09T06:49:26Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Allen\_Thomas](https://avatars.discourse-cdn.com/v4/letter/a/e19adc/32.png) [@Allen\_Thomas](https://forum.inductiveautomation.com/u/Allen_Thomas)\
**Post date:** [September 9, 2025, 6:49am UTC](https://forum.inductiveautomation.com/t/bulk-modbus-tags-adding/110475/1 "2025-09-09T06:49:26Z")

</div>

I’m working with **MODBUS TCP** to communicate with different PLC that contains approximately **30,000 registers**. I need to bring these registers into **Ignition as tags** , but I’m running into a couple of challenges:

- The registers are not arranged in a consistent order.

- Some registers represent single holding values.

- Others require **bit-level mapping**.

What would be the most effective approach to structure and manage these registers in Ignition, considering these constraints?

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [September 9, 2025, 12:50pm UTC](https://forum.inductiveautomation.com/t/bulk-modbus-tags-adding/110475/2 "2025-09-09T12:50:10Z")

</div>

I would use my spreadsheet import tool from the Exchange. Where you have any patterns of multiple registers, make UDTs that have a start offset parameter.