Do not begin by importing the entire API catalog. Prepare only what is required for one representative Project:
Identify the current source and one representative API asset.
Select the target Team and Project owner.
Confirm General Mode or Spec-first Mode before creating the Project.
Identify the environments, authorization, secrets, local files, and scripts required to use the pilot APIs.
Record who will validate the imported content and own any migration gaps.
Confirm the deployment using the Enterprise Onboarding Journey. For Apidog On-Premises, verify feature availability and navigation before following SaaS-specific steps.
Apidog should fetch selected workspaces, Collections, and environments from Postman. This is suitable when migrating multiple assets.
Exported files
The migration will use exported Collection v2.1 JSON and environment files. A folder can be uploaded when it contains the related files.
1.
Select the Collection and required environments for the pilot.
2.
Import through the approved Postman API or exported-file method.
3.
Review the import preview and base URL handling before confirming.
4.
Select the correct Apidog environment and send representative requests.
5.
Review the imported structure, variables, authorization, examples, and scripts.
Local form-data file references can be imported, but the local files are not uploaded automatically. Confirm those files separately before the team relies on the imported requests.Use Import from Postman, Manual Import, and Import Options for the detailed procedure.
Use this route when an OpenAPI or Swagger document is the portable API source.
1.
Confirm whether the specification will remain the source of truth.
2.
Import a JSON or YAML file, paste the specification content, or provide a raw specification URL.
3.
Preview the parsed endpoints and select the content to import.
4.
Choose the duplicate strategy for matching endpoints: Overwrite, Merge, Keep Both, Ignore, or Overwrite Selected.
5.
Validate paths, methods, schemas, examples, security definitions, and representative requests.
An OpenAPI document does not necessarily include the team's automated tests, secret values, local files, database or proxy settings, runner configuration, notifications, or collaboration settings. Record required items that must be configured separately.Use Import OpenAPI Spec, Spec-first Mode, and Import Options for the detailed procedure.
Do not assume that an import transfers every secret, local value, test, script, integration, or tool-specific setting. Review the import preview, record gaps, and keep a recovery copy before using overwrite options or removing resources that are missing from the source.
Do not configure Scheduled Import until the manual pilot import has been accepted.
The pilot Project was created in the approved mode.
The representative asset was imported through the selected route.
Representative users can find and open the first real APIs.
A representative request runs, or the blocking gap has a named owner.
Required environments, variables, and authorization have been validated.
Secrets, local files, scripts, tests, and other migration gaps have been recorded.
The import route can be repeated for the next asset.
This phase is complete when a representative Project has been imported and validated and the organization can repeat the selected route for the next asset.
