If I understand correctly, what you are doing is very wrong.
If this is a multi user database, then there is one and only one way to deploy it correctly. Everything else is begging for problems. on the network you should have the back end datbase with nothing but tables in it. On each users local workstation they should have a copy of the most current front end. It has Forms, reports, modules, macros, and queries. The front end could have some local tables for user specific settings.
Each front end has links to the backend tables. In this way the user only pulls data files across the network. Now if you want to work on the front end and add new features you can do that at any time. When you are done just send the users the new front end.
However, if you are redesigning the back end then this is how I would do it. I would create my new back end with the new table structure. I would link to the tables in the existing database. Now since my tables structure is different I need to run append queries to push the data from the old table into the new table structure. Once done I delete the links.
However, I do not really understand what you are doing. Because if I import a table from one database into another the relationships automatically come across. There is only one method to import a table into another database, and does not involve Excel.
