scottayy wrote:My list consists of all pros for keeping the custom software.
- "If it ain't broke, don't fix it"
- Search Engine Optimization could be done much better than the millions of clone forums on the internet
- Much easier to customize, rather than searching for a specific mod or pre-existing code
- Huge hassle importing 1.1 million posts (with custom made bb, etc)
- Huge hassle integrating into the current system
- Identity. Lots of companies I presume pay big bucks for custom made software.
This is just my list. I really don't see any pros to switching for no real reason other than to switch. I told the client this but wanted to have some backup, or some other views presented other than my own, so he can make a good decision.
I'll play devils advocate then.
- It may be broke and you don't realize it. Slower, bad queries, incorrect (x)html, bad integration, etc
- Many existing forum software packages have had extensive work done on improving SEO, including pre-made mods, and papers on how best to do it. phpbb comes to mind in a big way here.
- Searching for completed code is easier than coding your own? That doesn't sound accurate.
- Hassle to import the posts, but perhaps afterwards, it will be easier to work with them, since most opensource forums have substantial work completed on dealing with your posts. Whether its export filters, mods, etc.
- Integration may be easier in some areas, and harder in others.
- Lots of companies pay big bucks to gain favor with the open source community, where running the software and offering up a few patches back to the main developers can do the same for free
- You can find a phpbb developer, or an ipb developer, relatively easily. Finding someone that has experience with your custom coded software? Looks like its just the people you already know.
- Code quality. Having external folks look at your contributions will usually improve the quality, since not everyone tests on 16 databases, 12 web servers, and seven operating systems.
- Learn a marketable skill. If I know you've worked on code I am familiar with, that means something to me. If you've worked on custom code, I know very little about your skill.
I'm actually in the 'if it ain't broke, don't fix it' camp, but since you asked for the opposite viewpoint, there are some arguments for it.