History: Why Not

We routinely get questions about why a component is picked or not picked for WikiSuite. When a component has a direct alternative, it will be explained on a page such as Why Openfire. But in some cases, the potential app doesn't line up neatly with what we picked. This page is to explain.

SuiteCRM

See also: https://community.sugarcrm.com/community/news/blog/2018/04/06/sugar-community-edition-open-source-project-ends

SuiteCRM tas tons of features that are geared towards the CRM use case.

• https://docs.suitecrm.com/user/core-modules/
• https://suitecrm.com/solutions/role/marketing/

We don't add to WikiSuite because there would be way too much overlap, and it would add complexity. Pretty much all these features are either

• available in Tiki Wiki CMS Groupware
• easily configurable via http://tikitrackers.org/
• and the few features that are missing, let's add them

Dolibarr

Dolibarr is a CRM/ERP written in PHP with broad functionality.

We don't add to WikiSuite because there would be way too much overlap, and it would add complexity. Pretty much all these features are either

• available in Tiki Wiki CMS Groupware
• easily configurable via http://tikitrackers.org/
• and the few features that are missing, let's add them

Dolibarr has good the plugin route: https://www.dolistore.com/ where as in WikiSuite, we prefer integrated solutions to avoid http://pluginproblems.com

Odoo

Why not use Odoo for the Accounting functionality of WikiSuite? Please see WikiSuite vs Odoo.

See also

• Why
• Why ClearOS
• Why Cyrus IMAP and Cypht
• Why Free Libre Open Source software
• Why Openfire
• Why Syncthing
• Why Tiki Wiki CMS Groupware