# Migrate from Standalone to Fleet Managed

**URL:** <https://discuss.elastic.co/t/migrate-from-standalone-to-fleet-managed/366934>\
**Category:** Elastic Agent\
**Created:** [September 23, 2024, 6:47am UTC](https://discuss.elastic.co/t/migrate-from-standalone-to-fleet-managed/366934 "2024-09-23T06:47:50Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![kelvins](https://avatars.discourse-cdn.com/v4/letter/k/f19dbf/32.png) [@kelvins](https://discuss.elastic.co/u/kelvins)\
**Post date:** [September 23, 2024, 6:47am UTC](https://discuss.elastic.co/t/migrate-from-standalone-to-fleet-managed/366934/1 "2024-09-23T06:47:50Z")

</div>

I have an 8.15.1 cluster, with Fleet managing windows agents. However, the linux servers are installed with .deb elastic-agent packages. I hoped that there would be a guide for how one might move from standalone to fleet managed, but I cannot find.

I am comfortable with removing the deb package, and using the .tar.gz file to re-enroll the agent into fleet (along with deleting the old agent out of Fleet).

However, I want the agent to start from the last position (of the old agent) within the log files, and not start from scratch so as to not duplicate entries.

How would I go about achieving the outcome?  
Perhaps

- Stop the elastic agent (deb install)
- Backup the vault folder
- remove the debian package
- Change the policy that is installed to be nothing (ie maybe just agent logs)
- install the tar.gz package to register into Fleet management
- Copy the vault folder to the correct destination
- Change the profile of the agent to the original profile

Would that work?