Hi Haydee
I cannot really offer support throuhg the private message, if it is on the forum future users may benefit.
Basically consider everything
Static Data; Customers, Vendors, Items, BOM’s Routes, Contacts, Business Relations etc etc. The relationships are obvious, you need a customer record before importing alternate addresses.
Then you have dynamic data, opening balances (GL/AR/AP), opening stock, open purchase orders, opens sales orders, open production orders. How do you handle WIP/GRNI/GSNI. You need items, customers, COA etc prior to any of this. Then there is history and what you do with that (avoid it)
The table order depends upon the requirements. The “field” requirements you talk about depends upon the project, the customer data and the requirements of the customer.
Then you need to consider methods, how the data is presented to you, the timescales, the data verification etc.
Each business will have different approaches and methodology.
Data Import and Export tools are basic, they have issues and on the whole are not recommended for the more complex migrations, which in AX2009 could arguably include customers and vendors, as well as items. The business I work for do not use them for data migration projects, scripts are used because of the greater control, greater validation and overall time saving trying to resolve what the Excel import has done, but that is just a policy, whay you do is up to you.
You have encountered lots of issues already and if you are going to do this with no development input then it is going to be very long and painful for you and your customer (sorry).