Common Causes of Import Failures
Legacy devices often fail to migrate because of format mismatches, missing credentials, or outdated firmware that the cloud platform cannot interpret. The first sign is a non‑zero error code in the import log or a message stating that the device type is unsupported.
More from this site
Keep reading the latest coverage
Verify Device Compatibility
Check the Laurex device catalog to confirm that the hardware model is listed under "Cloud‑ready" devices. If the device is listed as "Legacy" only, you must upgrade its firmware before importing.
Update Firmware to the Latest Secure Version
Connect the device to Laurex Secure, then download the latest firmware from the vendor portal. Apply the update and reboot. Only devices running the current Secure firmware will expose the necessary APIs for cloud migration.
Export Correctly from Laurex Secure
Use the Secure Export tool to generate a configuration file in JSON or XML. Ensure the export includes all security certificates and key pairs. Omit any temporary tokens that expire during the export.
Import into Laurex Cloud
Navigate to the Cloud console's Import section. Select the exported file, confirm the device type, and click "Import." If the console reports a format error, re‑export the file or use the Cloud Import CLI with the --validate flag to diagnose the issue.
Common Error Messages and Fixes
| Error Message | Cause | Resolution |
|---|---|---|
| "Unsupported device type" | Device not listed as Cloud‑ready | Upgrade firmware or contact support for a compatibility patch |
| "Certificate mismatch" | Exported certs differ from Cloud expectations | Regenerate certificates in Secure, re‑export, and retry |
| "Import timeout" | Large configuration or network latency | Split the import into smaller batches or increase timeout settings |
Best Practices for Future Migrations
Maintain a migration checklist: verify compatibility, update firmware, export with all security artifacts, and test the import on a staging instance before production. Document each step to streamline troubleshooting and reduce downtime.