# Dashboard 2 Migration using AI?

**URL:** <https://discourse.nodered.org/t/dashboard-2-migration-using-ai/96235>\
**Category:** Dashboard\
**Created:** [25 March 2025 05:22 UTC](https://discourse.nodered.org/t/dashboard-2-migration-using-ai/96235 "2025-03-25T05:22:28Z")\
**Posts on this page:** 1\
**Showing post:** 23

<div class="post-metadata">

**Author:** ![thebaldgeek](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/thebaldgeek/32/93523_2.png) [@thebaldgeek](https://discourse.nodered.org/u/thebaldgeek)\
**Post date:** [28 March 2025 14:17 UTC](https://discourse.nodered.org/t/dashboard-2-migration-using-ai/96235/23 "2025-03-28T14:17:27Z")

</div>

> [@gregorius](#):
>
> Not many I would say.

I disagree. I think a lot of folks have / are going to turn away from NR when faced with Dash 2.  
Its interesting to see so many echo my findings from a year ago (I started rebuilding my dash 1 website in dash 2 on March 24th 2024 - a year later and I'm not even close to having parity).  
If I had to start with dash2 out the gate, I am quite sure my site would not have been built or ended up where it is today.

> [@craigcurtin](#):
>
> Each time i try and make a start on DB2 is feels overwhelming - as it feels that there is a LOT more background UI knowledge that is needed/assumed to achieve something reasonable.

This well states what I have been struggling to describe. Dash2 raises the no code/low code bar into programmer / programming experience required territory.  
It seems to put it on the same level as UIBUILDER.  
I never felt the need to retain a programmer on staff till I got to working with Dash2.

I've put my 'responsive' bugs and glitches on the github, but it's hard to put a ticket in for the impressions and experiences shared in this thread.

I guess I just want to say @craigcurtin its not just you, there are quite a few that feel this way, so be encouraged to just keep picking up the mouse and whacking at dash2, you are not alone.

For 'migration' from dash 1 to dash 2, I just have this critical (for my site) tip.

> [@Dashboard load times \> 30 sec with more than 250 connections to website](https://discourse.nodered.org/t/dashboard-load-times-30-sec-with-more-than-250-connections-to-website/92305/51):
>
> (slight aside - in the original dashboard 1 - it originally only sent the msg.payload/value to the front end - which restricted it quite a lot traffic wise (no large .req or .re objects etc) - but then of course people wanted .label and other things - and in the end we sent label, classname, format, colour, units, tooltip and icon... but that was all...)

Be aware that dash2 'leaks' ALL the msg.xxxx data to the browser. You can end up sending a LOT of crud over the wire that you never intended.  
Clean up your msg payloads BEFORE sending it to a dash2 node.

---

_[View the full topic](https://discourse.nodered.org/t/dashboard-2-migration-using-ai/96235)._