Skip navigation

How fits into your current toolset?

3 min read
Download PDF

When you select as your new headless CMS, there are many questions you may have. 

  • How do you integrate with your existing toolset that works well for you?
  • What about your existing content and technology infrastructure? 
  • Can you widen the range of tools for your operations after you move to 
  • What technologies are you going to use after the move to Are there SDKs? APIs?

This article is here to answer all these questions you may have about the transition to, your new CMS.

Table of contents

    Can you keep your existing toolset?

    You may already have your tools for content search and discovery, SEO, marketing, billing, and so on. This toolset works well for you.

    Now, the question is, can you use these tools even after you switch to Yes, sure! You can keep using most of the specialized services also under Unless you have all the services hard-coded into a single monolithic legacy CMS, that is.

    You can integrate with all kinds of services. is a headless CMS that loves the microservice architecture. is your central content hub where you create and manage your content, but you also augment it with various 3rd-party services.

    If you're a developer who's more interested in the technical aspect, have a look at the integrations hub. There, you'll find all kinds of services that you can integrate with

    What happens to your content and technology infrastructure?

    You can import the content you already have into including the structure of the content.

    Before importing your content, you'll build a content model that corresponds to the structure you need your content to have. It's also possible to let your developers import a content model. Then, your developers can migrate your content into the content model in

    As for the technology infrastructure, it's similar to the options about keeping the existing tools we've covered above. You can integrate a wide range of services into so that the continuity from the technological point of view is ensured.

    What about APIs? SDKs? itself serves as a content repository and content management system that provides access to the content via REST APIs.

    As such, doesn't bind you to any technology for developing your customer-facing apps and websites. The SDKs are in a couple of the most common programming languages, such as JavaScript and .NET. However, you're essentially free to choose any tech stack you like as long as it's able to work with REST APIs.

    Have a look at the introduction to app development for more details.

    How about marketing?

    No problem! enables you to connect all kinds of services you need to make your content perform the best.

    Some parts of the marketing scenarios are done using the built-in functionality, such as linking content items. The rest is managed by the best-of-breed tools of your choice.

    You can personalize content and integrate marketing automation with Pardot, analyze your content with Google Analytics, or evaluate your A/B test results using Google Optimize.

    See our article about marketing scenarios to learn more.

    What's next?

    You've learned that most of the services that comprise your current technology landscape can be integrated into With that concern resolved, you can continue to discover what offers to enhance your content operations:

    Got questions? Get in touch!