You should also manage your expectations. Access is more capable than LO. Moving tables to LO is like trying to get into a tight shoe with a big foot. It can be done if you skinny up the foot first. Recreating queries, forms and reports is a challenge, and this depends to a measure on how complex your stuff is.
There are several ways to migrate tables but I’ve not yet found one that works perfectly in all cases without some fixup once the migration is done. I think the last time I did it was w/ this tool that works pretty good, but is NOT perfect.
There are a number of gotchas in addition to the ones R mentioned. Watch out for field conversions, like for yes/no fields or currency. Also first clean your table names of special characters like colons. And you will have issues with case if you are not careful. Suggest dumbing down your Access first, then trying to migrate. Also LO can’t use =date() or =time() as a timestamp default. This can be done in MariaDb/MySQL but it isn’t as clean as in Access, i.e. only once the record is saved and refreshed will you see the default date/time inserted. Also watch out as you might loose your field comments and have to manually copy them over.
Forms have most all functionality as Access, but Reports seem to lack ability to grow and shrink with data, e.g. note fields are always of fixed height.
Also, so far, I haven’t figured out how to build macros that can be used inside query fields like was so handy in Access. For example I had a set of macros called things like:
LastFirstName(First, Middle, Nick, Last) which would properly format a name from components into something like: Smith, Ron “Ronny” A. Now this has to be done in SQL which is less capable.
Tools like HeidiSQL work quite nice to help you along and runs in both Windows and Linux, but watchout for database names with spaces in them, and other special characters in table names which can cause issues.
Also you will loose lookups and other properties. LO does not have the ability to add a field lookup (pull down) in tables like in Access (to help you insert ID from human readable text, like for example when you are converting State codes like CA to 42). You will have to build a form to replace this functionality which is 20 times harder than doing this in Access.
I could go on, but I’ll stop there.
But all that being said, I have converted some of my Access to LO and I’m working on the rest.
It has been a painful process, but things are gradually looking up.
I am committed to moving away from Windows ever since W10 was shoved down our throats, with it’s “run my CPU like crazy whenever it wants” policy, coupled w/ forced updates. It just began to feel like my machine was now owned by MS, even though I paid for it. …end of rant.