Hey @jarod.tulanowski !
Moving from Revit 2023 to Revit 2026 is a HUGE leap. Especially in terms of changes. Looking at Dynamo alone, that is a jump from 2.16.x to 3.6.x.
That is several minor release, and a major (2 → 3) release. So (unfortunately) some breakage is bound to occur.
I agree with @Ewan_Opie regarding taking this time to re-evaluate your graphs and migrate them to nodes that are now OOTB (where/when available).
Re: Custom packages. These will definitely need to be audited during your upgrade process. Unfortunately by the looks of it, archi-lab has not been updated in a little bit. I would reach out directly to @Konrad_K_Sobon 's github here and ask nicely - GitHub · Where software is built. (keeping in mind that packages are created most often as a side project, and in the author’s free time)
For each package you have used in your graphs, you will need to take a look and see what is available. Over the last 1-2 years we introduced package compatibility on the package manager, but not all packages have adopted it yet. So the question marks on the PM re: compatibility indicate that the author has not expressed this.
For python nodes in your graphs (custom packages, etc). Extracting the python seems like a good idea at first, but now you would really be on the hook for keeping that up to date. So, for that reason, it is not something I suggest doing.
What kind of workflows do you have and are needing to migrate?