Data Migration from Stoplight
It is possible to transfer data from your Stoplight workspace into a Swagger organization, for use in Swagger Studio and Swagger Portal. This section describes the available migration options and best practices for transferring assets. While Swagger supports importing multiple resource types, it is recommended to review and validate your data following a transfer, as exact alignment between the systems cannot be guaranteed.
Transferable resources
You can transfer the following types of resources to Swagger:
OpenAPI definitions
Markdown files
Spectral style guides (rulesets)
Data migration is not available for the following:
JSON schemas
Component libraries - which function as domains in Swagger Studio
Users and permissions
Masking
Prerequisites
If you are new to Swagger Studio, begin a trial subscription. Create a new organization to hold your assets.
If you are already part of an organization in Swagger Studio, ensure you are assigned one of the following organization-level roles: designer or owner. (The owner role is set by default in the trial plan.)
Migration methods
Use one or more of the supported migration methods to meet your requirements. The available transfer options include:
AI-assisted: Hydration through AI-powered features.
Manual: Based on manual export and import.
Hybrid: Implementing manual export, followed by import through Swagger Registry API.
Automated: SCM-based.
Support-assisted: Performed by SmartBear Support upon request through a support ticket. Only APIs and Markdown files can be transferred using this method (support for transferring Spectral style guides is coming soon).
Support-assisted migration
To request a migration of your APIs and Markdown files by our Support Team, submit a ticket on the Swagger support page. Include your Stoplight workspace name in the request. Ensure you have an active subscription prior to submitting the ticket.