Explore.cli imported Postman consistently getting 400/500 when Export to SwaggerHub

We inherited a legacy API with no swagger docs but fortunately we have a Postman collection.
We were able to use explore.cli to import the collection into APIHub Explore with the recent folder changes.
However, we are consistently getting 400/500 errors when we try to import the collection from APIHub Explore into SwaggerHub to generate the OpenAPI 3.0.

I was able to generate a test Space using History and export those to SwaggerHub. I suspect it maybe due to how the Postman collections are done for our internal ease of use? e.g. We use variables {{host}} and that doesn't seem to translate after import by explore.cli.

Here is the snapshot: link.

Here's some examples of 400 responses:
{"type":"https://problems-registry.smartbear.com/bad-request","title":"Bad Request","detail":"Cannot deserialize value of type `java.lang.String` from Array value (token `JsonToken.START_ARRAY`)\n at [Source: UNKNOWN; byte offset: #UNKNOWN] (through reference chain: io.swagger.v3.oas.models.media.Schema[\"properties\"]->java.util.LinkedHashMap[\"sites\"]->io.swagger.v3.oas.models.media.Schema[\"items\"]->io.swagger.v3.oas.models.media.Schema[\"properties\"]->java.util.LinkedHashMap[\"current_start\"]->io.swagger.v3.oas.models.media.Schema[\"type\"])","status":400}

{
    "timestamp": "2025-02-14T22:22:13.972+00:00",
    "status": 500,
    "error": "Internal Server Error",
    "path": "/spaces-api/v1/exports"
}