How do I resolve Labview load conflicts

How do I resolve Labview load conflicts

I am developing a data acquisition program in Labview that uses multiple
translation stages, cameras, a high speed digitizer, and other
instrumentation. I'm developing the application on one computer, and will
be deploying it to another computer. The development computer has labview
2013, and computer the application will be deployed on currently has
Labview 2012, but we will be upgrading it to Labview 2013 when we move the
application over there. Some of the drivers need different versions of the
driver to function under Labview 2012 than they do for Labview 2013. I'm
trying to keep all of the vi's, subvi's, and drivers for the
instrumentation in one directory tree so that I can move the whole tree
over to the computer it will be deployed on.
When I load the project in Labview I'm getting a lot of "Resolve Load
Conflict" dialog boxes popping up. When I go to investigate, Labview says
it can't find one of the files that is causing the conflict, but yet it
popping up the dialog. An example is below:

This happens every time I load this project - saving all doesn't enter the
new paths into Labview. I also tried creating a new project, and pulling
these vi's in, but the new project has the same load conflicts.
Evidently Labview or these vis think that these vi's that no longer exist
are still there.
How do I fix my project, vi's, or Labview so that it only uses the vi's
that it should, and I don't get all of these conflicts, many of which are
with nonexistent files?