Introducing GraphQL does not require an organization to remove every REST endpoint. Different interfaces can serve different consumers and operational needs.

GraphQL can provide flexible client-driven aggregation while REST may remain useful for simple resource APIs, file downloads, webhooks, public integrations, or infrastructure endpoints.

The important architectural principle is to choose the interface based on the problem rather than treating one API style as universally correct.