> For the complete documentation index, see [llms.txt](https://docs.nfh.global/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nfh.global/build/onboarding/switching-paths.md).

# Switching onboarding paths

Move an NFO or NP between the hosted (dedi.global) path and the file-based path without leaving the NFH fabric.

An entity may adopt either of the two onboarding paths onto the NFH fabric, and may switch between them at any time. An entity (NFO or NP) cannot simultaneously use the hosted (dedi.global) and file-based paths for any write operations — so a switch always ends with exactly one active write path.

In both directions, you first establish your presence on the new path, then remove it from the old one.

```mermaid
flowchart LR
    H["Hosted<br/>(dedi.global)"] -- "1. Publish files on your domain<br/>2. Remove namespace verification" --> F["File-based<br/>(own domain)"]
    F -- "1. Set up namespace + registries<br/>2. Verify DNS TXT<br/>3. Remove files" --> H
```

## Moving from dedi.global to file-based

{% hint style="info" %}
There is a one-time delay of about 15 minutes while the switch takes effect.
{% endhint %}

1. Publish your DeDi index file and the corresponding registry on your own domain, as described in [File-based onboarding](/build/onboarding/file-based.md) — a Beckn Subscriber registry if you are an NP, a Beckn Subscriber Reference registry if you are an NFO.
2. Log in to [publish.dedi.global](https://publish.dedi.global/), click on your namespace card, select **View TXT**, and remove the verification.

Your registry URL changes form when you switch — from `api.dedi.global/dedi/lookup/<domain>/<registry-name>` to `<domain>/dedi/<registry-name>` (see [Registry URL forms](/build/onboarding/file-based.md#registry-url-forms)). If you are an NP, share the new URL with your NFO so it can update its reference record in the network registry.

## Moving from file-based to dedi.global

1. Log in at [dedi.global](https://publish.dedi.global/) and set up your namespace and directories as described in [Hosted onboarding](/build/onboarding/hosted.md).
2. Complete the DNS TXT verification.
3. Remove the DeDi files from your domain.

The same applies in this direction: your registry URL changes to the hosted lookup form, so if you are an NP, share the new lookup URL with your NFO.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.nfh.global/build/onboarding/switching-paths.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
