help removiing TeamsOS from 5.0x

[mjel]

Hello,

We upgraded from 4.5.1 to 5.0.0c - and in hindsight - we should have removed TEAMS OS before hand.

I can not remove it using the loader - on a test site - i removed it manually form the folders to confirm my susupcions that it cause more problems - which it did .

can someone tell me how to remove this module from 5.0.0c - when i use teh module builder - the site hangs - as does my server at this point - i suspect that MYSQl is taking all the server resources.

i no longer have an assigned to - option in the layout - just assigned to team - the tables are fine - i think - but certainly there is confusion in the system.

hope some kind soul can help.

Kind Regards,
michael

[kbrill]

Several options are avaialble

1) restore a backup of 451 and start over
2) Uninstall by hand, unless you know what you are doing the best way is it install a fresh 451 and teamsos on a test database and see what files are in the custom directory, then go through the 5.0 instance and edit/delete those files. Any file that only deals with teamsos can be deleted, but if there are other lines of code that deal with other things then you will have to manually edit out that other code. Unless you have other modules loaded there should be few of these if any.

do backups first. If you have trouble post a zip of your custom directory and I'll see what I can do.

[mjel]

Thank-you very much -- i will go through you steps and folllow up wiht you -

tahnks again,

Michael

[sacramentojoe]

Boy, Am I glad I read this post before upgrading. But I have one more question.
I'm in the process of upgrading to Sugar 5 PRO. Is there a tool that will copy my teams / contacts / leads relationships to work with the built in teams in pro?
I don't want to lose that data if possible.

Thanks.

[kenlyle]

I've got a similar situation, but have since done a couple of upgrades, and am now at 5.2.0

How about another approach...install a new 5.2 instance and point it at the old database? Then, theoretically, it would only be a matter of removing the TeamsOS info from the database, no?

Thanks,
Ken