Hi @geco06,
Sure, it would be a handy feature.
However, while the export part is easy to do, the import part is not. Besides shipping zones, methods, and rules, there is meta-data bound to products (such as shipping classes) used for shipping. A good import routine should somehow establish relations between the entities already existing in the system and the ones presented in the data we are going to import.
For example, what is the expected state after syncing (i.e., export, then import) a website A to a website B:
website A (state before export):
Shipping zone 1 — Name: “EU”, Locations: “UK – Avon”, Id: #1
— Shipping method 1 — Name: “weight-based shipping”, Type: WBS, Id: #10
website B (state before import):
Shipping zone 1 — Name: “EU”, Locations: “UK”, Id: #13
— Shipping method 1 — Name: “Flat Rate”, Type: built-in Flat Rate, Id: #10