Level 2 Data Unit Overlap Help - Data Loss

Channels is likely what you want. They allow you to segregate data by Account and/or one UD dimension. Assuming your loads target different UD intersections for at least one dimension (since you say Accounts overlap), you can ensure that different loads will be guaranteed not to step on each other's toes. Give another read at the page about Workflow Channels , you'll find a section called "Workflow Channel User Defined Phasing"; I'd try to implement that, then combine it with Account phasing if necessary. Make sure you also read the bit about the standard channels (NoDataLock etc), because you'll probably want them in some profile to keep things sane. This is also covered in the Foundation handbook, and there is probably material on Navigator too.

Channels can be a bit mind-bending to implement, particularly when they get added to an existing application; so expect some breakage of existing customizations (e.g. "this dashboard worked fine but now it won't allow me to enter data!" "Yes, because it's now in the wrong profile for the channel it affects..."); but they are super-powerful and will allow you to solve this kind of situation in a very robust way.