A CRM with a single contact table with two different scope | Will this be advisable?

My org has a need for a CRM, but two different scopes. The scopes are (i) case management of student records, (ii) donation/grant management.

The CRM has a module for (i) case management of student records, and (ii) donation/grant managements. Both modules can be installed at the same time and are connected to the same database instance. However they will use the same Contact table.

My issue is that the scopes are different. There is no real overlap between the contacts (students vs donors). And I sense that it would be a mistake populating both of them in the same contact table.

Any thoughts or advice?