Importing a Postman environment to ReadyAPI

Without the actual file all I can do is guess, but...!
Try this:

- Re-export that problem environment from Postman:
Use a standard JSON export (not a .env or VS Code format).
• Make sure the file has a values array with objects like { "key": "...", "value": "...", "enabled": true }. (Some newer exports add fields like type/secret—they’re fine in the latest plugin but can break older ones.)

- Open the JSON and normalize the variables:
• Remove duplicates (same key appearing more than once).
• Delete any entries with a blank/whitespace key, or where key is missing.
• Trim leading/trailing spaces from key names.
• Temporarily remove variables with exotic type values (e.g., secret) if you’re not 100% sure you’re on plugin ≥3.1.0. Re-add them in ReadyAPI after import. (3.1.0+ should handle them; older builds won’t.)

- Make sure you’re on the current plugin & a supported ReadyAPI:
• ReadyAPI ≥ 3.60 and Postman Plugin 3.1.x. Update via Integrations → ReadyAPI Postman Plugin

- Retry the import with Copy endpoints from ‘No Environment’ unchecked first. If it imports cleanly, then go back to Environments in ReadyAPI and set endpoints for that env. (Endpoints live in ReadyAPI environments alongside properties.)

If it still fails, import the Postman collection first, then import the environment (so the project/entities exist), which can help the mapping step.

Let me know how that goes!