Splunk® Enterprise

Forwarding Data

Download manual as PDF

Download topic as PDF

Migrate a Windows light forwarder


You can migrate checkpoint data from an existing Windows light forwarder (version 4.0 or later) to the universal forwarder. For an overview of migration, see "Migrate from a light forwarder" in this manual.

If you want to migrate, you must do so during the installation process. You cannot migrate post-installation.



What the installer does


1. Searches for an existing heavy or light forwarder on the machine.

2. Determines whether the forwarder is eligible for migration (must be at version 4.0 or above).

3. If it finds an eligible forwarder, the GUI offers the user the option of migrating. (The command line installer looks to see whether the MIGRATESPLUNK=1 flag exists.)

4. If user specifies migration (or the MIGRATESPLUNK=1 flag exists), the installer shuts down any running services (splunkd and, if running, splunkweb) for the existing forwarder. It also sets the startup type of the services to manual, so that they don't start up again upon reboot.

5. Migrates the checkpoint files to the universal forwarder.

6. Completes installation and configuration of the universal forwarder.

What you need to do

At the end of this process, you might want to perform additional configuration on the universal forwarder. Since the migration process only copies checkpoint files, you will probably want to manually copy over the old forwarder's inputs.conf configuration file (or at least examine it, to determine what data inputs it was monitoring).

Once the universal forwarder is up and running (and after you've tested to ensure migration worked correctly), you can uninstall the old forwarder.

Remotely deploy a *nix universal forwarder with a static configuration
Migrate a *nix light forwarder


Was this documentation topic helpful?





0 out of 1000 Characters