# Transfer Document types b/w environments (Import/export) **URL:** \ **Category:** Experience Manager (PaaS/OnPrem)\ **Created:** [March 29, 2022, 2:03pm UTC](https://community.bloomreach.com/t/transfer-document-types-b-w-environments-import-export/3112 "2022-03-29T14:03:02Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![nags\_br](https://yyz1.discourse-cdn.com/flex027/user_avatar/community.bloomreach.com/nags_br/32/1166_2.png) [@nags\_br](https://community.bloomreach.com/u/nags_br)\ **Post date:** [March 29, 2022, 2:03pm UTC](https://community.bloomreach.com/t/transfer-document-types-b-w-environments-import-export/3112/1 "2022-03-29T14:03:02Z")
Hi, Is there a Programatic way to export/import DocumentType B/w environments . Was using ([Hippo Content EXIM (EXport/IMport) Documentation – Command Line Examples To Export Content](https://bloomreach-forge.github.io/content-export-import/cmd-example-export.html)) and see can export /import documents via zip are working . Is there a programatic way to export and Import DocumentTypes as well ? ---
**Author:** ![jeroen.hoffman](https://yyz1.discourse-cdn.com/flex027/user_avatar/community.bloomreach.com/jeroen.hoffman/32/43_2.png) [@jeroen.hoffman](https://community.bloomreach.com/u/jeroen.hoffman)\ **Post date:** [March 30, 2022, 8:07am UTC](https://community.bloomreach.com/t/transfer-document-types-b-w-environments-import-export/3112/2 "2022-03-30T08:07:50Z")
Hi, Don’t think export/import document types is supported by the plugin. Such function might be possible but it needs a thorough understanding of the internals. Main issue is that there’s not only /hippo:namespaces configuration but also cnd entries, quite tricky to do programmatically. It’s done in our bootstrapping process, so maybe just doing deployments is an easier way for you. Jeroen ---
**Author:** ![nags\_br](https://yyz1.discourse-cdn.com/flex027/user_avatar/community.bloomreach.com/nags_br/32/1166_2.png) [@nags\_br](https://community.bloomreach.com/u/nags_br)\ **Post date:** [March 30, 2022, 12:16pm UTC](https://community.bloomreach.com/t/transfer-document-types-b-w-environments-import-export/3112/3 "2022-03-30T12:16:13Z")
Thanks Jeroen, “doing deployment” do we mean Manually moving the export or Import of xml/yaml/zip from console. Is there any other way apart from manual deployement or something this doesnt require manual intervention ? ---
**Author:** ![machak](https://yyz1.discourse-cdn.com/flex027/user_avatar/community.bloomreach.com/machak/32/1298_2.png) [@machak](https://community.bloomreach.com/u/machak)\ **Post date:** [March 30, 2022, 12:33pm UTC](https://community.bloomreach.com/t/transfer-document-types-b-w-environments-import-export/3112/4 "2022-03-30T12:33:20Z")
> [@nags\_br](#): > > Manually moving the export or Import of xml/yaml/zip from console. No, it means: deploying your changes via deployment. > **[Deploy a Project Distribution - Bloomreach Experience Manager...](https://xmdocumentation.bloomreach.com/library/deployment/deploy-a-project-distribution.html)** > > The fast and flexible on-premise or PaaS headless CMS (edit: corrected link) Console is not meant for moving content etc. it is just meant for quick fixes. Content shouldn’t be moved around and should be entered on in your production system. You can put it behind firewall etc. if needed and separate it from facing pubic access directly. If you run enterprise project, you can use content replication plugin for moving content around. > **[Release strategies for content and configuration updates - Bloomreach...](https://xmdocumentation.bloomreach.com/13/about/release-management/release-strategies-for-content-and-configuration-updates.html)** > > The fast and flexible on-premise or PaaS headless CMS ---
**Author:** ![PCentgraf](https://yyz1.discourse-cdn.com/flex027/user_avatar/community.bloomreach.com/pcentgraf/32/55_2.png) [@PCentgraf](https://community.bloomreach.com/u/PCentgraf)\ **Post date:** [March 31, 2022, 6:53am UTC](https://community.bloomreach.com/t/transfer-document-types-b-w-environments-import-export/3112/5 "2022-03-31T06:53:12Z")
See also my answer to a similar question here: > [@Import/export of a document/document types from one env to another env](https://community.bloomreach.com/t/import-export-of-a-document-document-types-from-one-env-to-another-env/3104/2): > > The ability to import and export content types via API is available in our SaaS product, but not in the brXM on-prem / PaaS product. The expected mechanism for updating content types in brXM is via the deployment and bootstrapping mechanisms that require a process restart. More details are documented below. We tend to refer to this by the term “namespace”, since content types are typically organized into CND files that include multiple types organized by a common name prefix. Note that you ca…