I’m currently using Cockpit CMS as my headless CMS, as at the time it was built, repeater fields were not available in Strapi and that was a hard requirement.
At this time, Strapi has outpaced Cockpit in maturity and features and I would like to make the switch, however my Cockpit instance is fairly complex as entries have relationships with other entries (collections in Cockpit language).
Any resources on how to import or has anyone built an importer?
We don’t currently but were just having this conversation internally. Migration is a very tricky process, though entirely possible.
For the moment I would suggest handling this by hand by building out the model structure and doing a lot of testing before pulling the trigger on a hard migration. Eventually we do plan to build out tooling to help users with migrating but there is a lot the Strapi project needs to do before this.
We prefer to do things clean and correct instead of fast and messy 
Hey, just wanted to see if there has been any change in this? My company is also using Cockpit CMS with a custom plugin adds some extra pages. The documentation and support over there is pretty minimal… Plus it’ll be nice to get away from PHP.
I think I need my first plan of attack is to convert or MongoDB to MySQL at V3 per your documentation, then upgrade to V4. If I can retain all of our data I can then add custom pages to the Strapi interface (it’s nice for our folks to be able to edit types) or create a separate front-end.
Any thoughts/advice is appreciated.