Just noticed replies to this requesting information.

Yes we did migrate our QuickFields processes and schedules in QuickFieldsAgent.  

Step 1 is to get with your VAR to get a temporary 2nd License if you don't already have one. 

Step 2 is to really evaluate your scheduled sessions to see if they are actually doing useful work.  If not, disable them and don't move them. (This might be the REAL step 1!!!!)

After that,  I had to import more than just the QF Sessions.  I had to get the QFA schedules imported as well, and if importing the QFA schedules, I also had to import the Windows Task Scheduler tasks.  On top of that, if the sessions required a DSN for a lookup, that will need to be rebuilt on the new server.  If you know a way to import that sort of thing, more power to you.  Best I could do was write PS scripts to identify the ones that needed to have a DSN re-created on the new server.  Thankfully I didn't have too many. 

So I created 3 folders on my old servers desktop: 

QFS

QFA

WTS

I populated each with the appropriate information. 

For QFS(sessions), I did exports from the old system, to import to the new system.

For QFA(Agent Schedules) I got them by finding them on the system where they are created, and copied them to the QFA folder.

For WTS(Window Task Scheduler tasks) I remember having to open up Windows Task Scheduler, and the tasks are easy to see as they (for me) were named "QFA8_<name of the QFA schedule>".  I did a right click on each and exported them to the folder.

(Side note: Take note of what version your WTS is.  When you open a task in Windows Task schedule it tells you some Windows Version information.  Make sure the old version stays the same on the new server even if it's a different version than the new server, or it won't work.  The good part is they are probably ALL the same.  Not going to guarantee that, but seems like a good chance you wont have 5 of one version, 28 of another and 1 of a third especially if they are all coming from the same old server). 

I think it was rather straight forward to import the QFS and the QFA, but the WTS required a bit of massaging.

Also, I don't recall actually "importing" the QFA,  I think it just got copied into the correct place on the new server. 

The new installation might point to a different working directory and/or name of the binary to run the QFS.  

I wrote a Powershell script to make that change in the WTS xml (in code block below, but I offer no warranties.  Use as reference only!)

From looking the script, I remember I created two new folders to keep track of things.

"From_OldQF" and "To_NewQF".  (could have been better named because I was working on the WTS's, not the QFS or QFA's here.

Anyway, I put all the Old WTS exports into the From_OldQF, and ran my script on them.  The output for the new WTS ended up in "To_NewQF".  Which was nice as I didn't harm the old WTS in case I need to re-run.

The script changed the Working Directory entry and the Command name.  It also only selected "enabled" WTS's (I had many disabled ones, and didn't feel the need to move those, after examination).

The script did however change the status from enabled=true to enabled=false as I didn't want the schedules to start running until I felt everything was in order. 

$odir = "C:\users\SvcLaserfiche\Desktop\From_OldQF"
$ndir = "C:\users\SvcLaserfiche\Desktop\To_NewQF"
$xdir = "C:\Program Files (x86)\Laserfiche\Quick Fields\Legacy"

Get-ChildItem -Path $odir -Filter QFA8_*.xml | ForEach-Object {
	[XML] $xml = Get-Content $_.FullName
	if ($xml.Task.Triggers.CalendarTrigger.Enabled -eq "true") {
		echo "Processing $_"
		$xml.Task.Actions.Exec.Command = "$xdir\QFMonitor.exe"
		$xml.Task.Actions.Exec.WorkingDirectory = "$xdir"
		$xml.Task.Triggers.CalendarTrigger.Enabled = "false"
		$xml.Save("$ndir\$_")
	}
}

I hope this helps!