Hi,
First all, BAT tool is not supposed to migrate the configuration data from one server to another.
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/4_1/bulk_adm/5_1_1/bat_ovr.htm
The only tools used to migrate the configuration data are BARS or MCS backup utility.
The BARS tool support callmanager version 3.3.x or above (3.3.2, 3.3.3, 3.3.4, 4.0X and 4.1x)
http://www.cisco.com/univercd/cc/td/doc/product/voice/backup/bars40/barsad40/index.htm
The MCS backup tool support callmanager version upto 3.3.x; NOT support callmanager 4.0 or above.
http://www.cisco.com/univercd/cc/td/doc/product/voice/backup/br3552/index.htm
You can use the BAT as some sort of backup tool. However, you can migrate only users and phones, no other configurations such as route pattern, partitions, CSSs....
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/admin/bulk_adm/5_0_1/bat_exp.htm#wp1066850
In this case, you export the phones or users using the BAT tool in 3.3(5) from the old pub and import the files back using the BAT 5.1.
However, please be aware that this method will be prone to errors, as the BAT tool version difference.
Here are some suggestions:
1.- Export the phones to a file.
2.- Export the users to a file.
3.- Import the phones without caring about the error "duplicate" error messages, if the
phone is associated to more than one users.
4.- Then import the users that will re-associate the phone.
5. If you have EM configured, please import the UDP after user import
As a note, CM 4.1 will have more attributes that it might does it differently.
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/admin/bulk_adm/4_4_4/bat_rbt.htm#wp1066850
But yes, it should work.
Check this:
http://www.ciscotaccc.com/kaidara-advisor/voice/showcase?case=K10566368
HTH
