Skip to content

Multi-Project Import #2734

@chayglass84

Description

@chayglass84

Jobs to be done (optional)

Clients often have hundreds or thousands of projects in Postman they want to bring to Git. We built a multi-project import for this that is hidden by default. Enterprise clients can ask their CSM for access. Pro and other clients can still use the rest of the process below, they'll just need to import one at a time.

The JIRA ticket for this work is https://konghq.atlassian.net/browse/INS-703 and associated subtasks.

  1. Export their data from Postman (this can be painful to get Postman to export all the data, and obviously we can't help here).
  2. Postman will export it as a giant blob of JSON files. They can run the separate tool we created in https://konghq.atlassian.net/browse/INS-1096 to organize those files into folders per project.
  3. The files are now organized. for the multi-project import once it's enabled... so under Preferences -> Data -> Import (or anywhere else you get to our normal import project screen) there's an extra button. Refer to 703 for the various ways that works. Projects do have to all be in the same organization for now (likely to be improved in the next 6-12 months). The whole reason we put this behind a flag is because this thing can handle 100 or 1000 projects at once, which means its easy to make a really big mess. People should be careful. :)
  4. That import also does a bunch of syntax transformation from Postman Syntax to Insomnia Syntax. We constantly update this list of transformations. There are some things we'll never be able to detect and transform - principally these are things that require the code to run for us to catch it (like say, concatenating two strings into a different value). There are some specific examples listed under the Unsupported Features section of this comment. Clearly, we shouldn't list everything we do and do not transform in the docs, no one wants to read or maintain that :)
  5. For Local and Cloud projects, clients are done. For Git projects, they still need to manually create and link a repo for each project. (Some investment coming here around EOY).

Definition of done

A How To guide that walks through this, with all the good and bad covered so people know exactly what to expect.

Due date (optional)

11.6 ships Sept 10, but this likely won't be needed on day 1, so let's say within a week of that.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions