First, take a step back and think about the SplendidCRM modules that would be created in DNN. You would effectively create over 100 SplendidCRM related modules (which is an Edit, Detail and List DNN module for every SplendidCRM module). Is that acceptable? Maybe it would be better to expect a full installation of DNN and SplendidCRM with limited module sharing.
Second, you would have to determine whether you wanted to go with the SplendidCRM ACL rules or the DNN ACL rules.
Third, you would have to decide how to handle the multi-portal issues. SplendidCRM was designed to require separate databases for each instance. It is not possible to have multiple SplendidCRM portals on a single database.
Fourth, from a license perspective, you would have to release under the SugarCRM Public License and you would have to ship the project with the SQL source code encrypted just as we do with our SplendidCRM Installation application.
There are some shortcuts that you could take.
1. You could require that all DNN portals share the same SplendidCRM instance.
2. You could allow both DNN and SplendidCRM ACL rules to apply at their respective levels.