# Is there a concept of "namespaces" or logically separating graphs in dgraph? **URL:** \ **Category:** Dgraph\ **Created:** [January 23, 2023, 6:29pm UTC](https://discuss.dgraph.io/t/is-there-a-concept-of-namespaces-or-logically-separating-graphs-in-dgraph/18200 "2023-01-23T18:29:03Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![rahst12](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/rahst12/32/2416_2.png) [@rahst12](https://discuss.dgraph.io/u/rahst12)\ **Post date:** [January 23, 2023, 6:29pm UTC](https://discuss.dgraph.io/t/is-there-a-concept-of-namespaces-or-logically-separating-graphs-in-dgraph/18200/1 "2023-01-23T18:29:03Z")
Hi, We’re considering a few different ways to reingest all the data we have in dgraph without standing-up a fully new dgraph cluster. Our process, in the past, has been to export Elastic JSON data, perform some transformations to get it into DGraph format, and then ingest it to dgraph - all of this was into a fresh/clean dgraph cluster. We were discussing that it would be a lot simpiler if we could reingest the data into the current dgraph cluster, but it be logically separated from the current data that is in there (a namespace?). I know there’s a concept of namespaces for enterprise dgraph with multi-tenancy, however, we don’t have the enterprise version and really don’t have a need for multi-tenancy from an organization perspective… I was hoping the community may have some thoughts suggestions here. Thanks, Ryan ---
**Author:** ![amaster507](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/amaster507/32/4123_2.png) [@amaster507](https://discuss.dgraph.io/u/amaster507)\ **Post date:** [January 23, 2023, 8:53pm UTC](https://discuss.dgraph.io/t/is-there-a-concept-of-namespaces-or-logically-separating-graphs-in-dgraph/18200/2 "2023-01-23T20:53:01Z")
Prefix your predicates and type names.