> For the complete documentation index, see [llms.txt](https://explore.notifyme.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://explore.notifyme.tech/adopting-notifyme/plan-the-software-adoption.md).

# Plan the software adoption

In order to effectively migrate from the actual management processes to the NotifyMe platform, **we recommend a phased approach** which will result in minimal/no disruption to day to day operations activities.

The following is a high-level overview of the phased approach:

1\.     Project Charter

2\.     Project planning

3\.     Project kick-off

4\.     Business/IT alignment

5\.     User Acceptance Testing (UAT)

6\.     Training and Roll-out

The milestones represent a clear sequence of events that incrementally build up until your project is complete by achieving the goal statement that has been identified.

As the project planning moves forward and the schedule is developed, the milestones and their target completion dates can be modified, adjusted, and finalized as necessary to establish the baseline schedule.

The Customer Success Team of NotifyMe may offer you support in the implementation and provide guidance and support to facilitate smooth execution of the adoption project.

![](/files/-MMuuME6RO9MxNuZXIq3)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://explore.notifyme.tech/adopting-notifyme/plan-the-software-adoption.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.