I should have been more clear about this, The exports with the lists are huge, often too big to be sent by email (using a script on the device that takes an export and emails it for backup). The issue is not the size on import, the issue is that (due to their size) it is difficult to get the exports from the device to a safe place.
I have been writing on a export and restore script for address-lists. It reduces the number of characters you need to backup/restore such a list.
I think that it is able to convert to static but I don't think it I already made it convert to dynamic. But that could be implemented. It is still beta and I did not spend much time on it more than a year now.
I made it it for the same reason to have smaller exports/backup. But then I am thinking why is that not a option on backup/restore or export/import to ignore address-lists. It chould be choice of the user to not export/import those lists.
Edit: checking my script I can make them dynamic but only with a time-out, RouterOS limitation on script/terminal, and then the max timeout is 35 weeks 3 days and 13 hours 13 minutes and 56 seconds. I can make that time as MAXimum when selecting restore as dynamic with a warning that the it will expire in time. This is implemented only for backup for making it easy to generate different address-list for different 'client' routers.
The help test:
Edit 2: the name of the address-list can not contain spaces or special control characters used in RouterOS.