Migrate 412 Config to 500v2

[CamIAm]

We have a IPO 412 that is being migrated to a new 500V2. I've been trying to manually create the config, on the new box, but it seems like an almost impossible task.
But I have recreated the 200 + extensions, as a starting point. I've read an earlier post saying that you could just push the config onto the new box. The merge seems to report errors whenever I try to do so. All of the licences have already been migrated. Has anyone else had any luck using this approach?

 

[tlpeter]

Upgrade the 412 to 6.1 ( not needed but I like to bring it as close to the new version) and then open this config offline and shoot it in the ip500.
It will ask you to convert it.


BAZINGA!

I'm not insane, my mother had me tested!

 

[CamIAm]

Thanks tipeter, Will I be able to get it to 6.1 from 4.2?

 

[tlpeter]

Yes you can do that.
You won't be able to make any calls after that because you do not have an upgrade license anymore but that is not a problem.

BAZINGA!

I'm not insane, my mother had me tested!

 

[trinetintl]

With the super old systems we have upgraded we had to use the export to CSV feature, kind of crude but it has helped us to keep everything clean. This is not probably the best option out there but it is there and it helps.

RE

http://www.trinet-intl.com

APSS - SME
ACIS - SME

 

[intrigrant]

As a alternative you can open two managers. one with the excisting config and one with a new ( empty ) config.
Copy the trunks, users, ICR and groups between the managers with Ctrl-C and Ctrl-V. Shortcodes and Directory can best be exported an imported.
But just pushing the old config to the new system works as well but then you still have to go trough all programming just to check if all is OK.
Licensing can be copied also, select all lics in excel, copy, then in the new manager click on licenses in the left pane and press Ctrl-V, voilá done.

If it ain't dutch it ain't much