Two other items not touched on...
1) Talk to the end users and find out what OUTPUTS (reports, exported data, what have you) they use and document this.
2) Once you know what they expect to come out of this system, do the same for INPUTS.
The best built system is useless if its not used. This list will help you identify what is really being used.
From there, look for supporting systems required to allow input/output.
If need be, create a blank front end and start importing reports. Find out what queries and tables they need. Then start bringing in forms that drive the reports.
I had to do something similar a few years back. Spent a month trying to work out what needed what in the existing system. Then I sat back and found out what was actually used. Created new front end and brought over the couple dozen objects.
Once that was working I removed the hundreds of odd reports and queries left over from previous visits of the "Good idea fairy". I couldn't believe how much... garbage had been left in there.