I have had this problem a million times. Or, actually less.
You really should read the export file carrefully.
For example, you HAVE to rename the interfaces as in your export files, PRIOR to importing.
Second, you HAVE to put security profiles for wireless BEFORE the wireless interface config, if you have wep or wpa set, or else you will receive error, because the security profile does not exist at that time.
There are many, many little details like that, wich will make your import of the export file a night mare.
I have put each export file into pieces, then put a name starting with a number for each piece, so as not to recieve this kind of errors.
Of course, you can import a file "arranged" with the proper order of the sentences, but this way i found it is harder to follow.
I guess MT stuff thought only to have a "clear text" configuration export, and not to actually importing, cause it's generally not working. Anyway, with a little work, it's done corectly. Thank you.
If there is any way that this could be fixed in a future release, meaning full export could be imported AS IS, ( with renaming the interfaces only), we should be very grateful.
Till then, put your export file like this:
and so on, putting in each script the proper part of the full export.
This way of keeping configuration will save you A LOT of your time, when you have to replace a router.
Also try to keep them updated. It's your time, and your money in.
If only for CPE use, you can always have a single "arranged" export file with default addresses of your choice, nat setting or routing, firewall settings, interface names ( default ones to be renamed acordingly: eg:
/inte set wlan1 name="uplink"
and so on, and you can import that file by connecting to the cpe in mac winbox, at first boot, or whenever you choose.
I am using this approach and .. as i said: my time, my money. ( or yours)