Thiago,
It's actually pretty straightforward. There is an upgrade tool (called PUT), that you download off of CCO that does the data and licensing extraction from the existing system. It's a lot like the migration assistant for the old CCM 4.X systems.
This will generate a TAR file that it pushes off to an SFTP server. Once you have the new system built, you'll log in for the first time USING THE APPLICATION ADMIN USER YOU PUT IN DURING THE BUILD...not Administrator/ciscocisco... and the first question it asks is whether or not it's an upgrade. If it's an upgrade, it will ask for the SFTP info for the TAR file (NOTE: When it asks for the path, make SURE you include the TAR file name as it wants the FULL sftp path. If you forget this, it will fail. This isn't well documented and quite frustrating to deal with).
Then it will ask you for the license file for the upgrade license. After that, it will put everything into the database and crank on up. You need to have CUCM up already before you do this so that it can talk to the AXL provider, etc.
Couple of notes about Windows to Linux upgrades:
1. File names are case sensitive in Linux. If your scripts call for a prompt named PromptName.wav, but the actual file is promptname.wav, it will fail.
2. If you use file paths, they will be different under linux. Linux doesn't recognize a C: drive. Also the slashes are / and not \ in file paths.
3. You have no real access to the file system. You can't record a prompt and then just go in via the temp directory and grab it like you could under Windows. You'll have to create or modify your prompt recording scripts to address this.
Licensing on v8 is tied to the MAC on the server. If you put it on VMWare, it's tied to the license MAC of the system. License MAC will change if you change any of the values that are used to build it (IP address, gateway, NTP server address, DNS server #1, DNS name, values in the Cypto Cert, etc.). It's a long list. Bottom line, if this applies to you, plan accordingly.
HTH
Cliff
