 <p>If the readonly and readwrite entities do not share relationships, the easiest solution is to put each group in their own configuration and then have separate stores. That way, updating is just a matter of swapping out the readonly persistent store file. </p> <p>If they do have relationships, then your only option is delete all the existing readonly and repopulate by building new objects on the fly. </p> <p>If you are designing from scratch the first option is usually best for pre-populated material. You can use objectIDs and/or fetched relationships to form pseudo-relationships across stores. </p>