The most immediate problem that you are going to have moving off of MSAccess to mySql is providing data access to your users, who are presumably using MSWin.
The solution I chose was to provide an equivalent Web interface (using Perl CGI scripts, but you could go with PHP, or Python, or Zope, or many other possibilities) for the MSAccess user interface. With the user interface taken care of in a database agnostic fashion, I was free to move the data to my database of choice.
If the burden of installing new SW on your user's desktops is not an issue, then you should checkout the Rekall product from theKompany (
http://www.thekompany.com/products/)