[IanMSpencer]

Ok ... I came to the same conclusion as you, but figured I'd ask incase I was overlooking something. I'll probably end up breaking up the book as individual songs and associating each set list with the specific song for the week.

If you can work out the spreadsheet programming, you might find that the import is easy enough not to fret - it's only bytes and it sounds like it is a long term, unchanging entry and the PDF will be shared.

If you can cut and paste the index into the spreadsheet, and calculate page numbers (are they single page, do they overlap, multi-page ending on a separate page from the next one where you can use the next entry) and format a from-to text field that MS will use. Use collections and or setlists to group the songs. If you check the CSV properly, you shouldn't have any maintenance to do in MS. 

I've got 1300 songs in my DB and it takes seconds to backup to the cloud (fast connection admittedly). 300 song entries will not overload the system and use of the collection, custom group fields and sensible naming can ensure that MS isn't an unmanageable mess.