Multiple companies, multiple databases? Maybe?

It seems like an obvious question. If a customer has two companies, then they will need two company databases in Dynamics GP, right? Well, in a lot of cases, yes. But in some cases, no. And the trick is to know which case applies to your situation.

I break it down to a variety of "tests" or points to consider when analyzing whether to have a database for each company or to combine several companies in to one database. Of course, combining companies in to one database is not incredibly common...but for a select set of customers, it really is the best solution.

Here is a cheat sheet I have put together that I use as a guide to the pros/cons and tests that I apply when helping a customer make a decision regarding the structure of their companies/databases.

Please feel free to share your own questions/tests that you apply to this decision as well! As always, thanks for reading :)