We support having multiple packages per TLD, but the package import tool only allows one per TLD. Instead we should allow one per TLD per module.

The import will look like this:

• Search for packages with registrar modules
• Start a database transaction
• Loop over the packages
• Check if the package is valid for import
  • The package must have at least 1 yearly pricing term
• Loop over each TLD assign to the package
• Check if the TLD is valid for import
  • The TLD must not already exist with a package assigned that is for the same module as the package being checked
  • OR The setting to override existing packages must be enabled
    • In this case the current package should be deleted (This may result in the TLD being deleted)
    • If deletion fails, the whole import should fail with an error
• Create a package with similar details assigned to the Domain Manager package group
  • The TLD/module_id must not have been imported from a different package already (keep a running list of tld => module_id => package_id)
• If the setting to migrate services is enabled, move all services that match the TLD from the old package to the new one
  • If there are no more services assigned to the old package, mark it as inactive
• End both loops
• Loop over each imported tld
• Loop over each imported module/package for the tld
• If the TLD does not exist, create it using the first module/package in the list
  • This may result in an inactive package being set as the primary for the TLD which is fine
• If the TLD already exists, add this package to the domains_packages table for the TLD
  • Mark this package as inactive

We should update the import text to explain the new process, that not all packages will be refelcted on the tld list page, that you can switch between modules, and how to view hidden packages to confirm the import