Write custom levels to individual json-formatted .level files

Instead of writing a database migration task, I intend to migrate the existing level set directly from the level-builder data as follows:

1.  Merge this feature into levelbuilder first (note: test runner will fail on seed)
1.  Generate the initial set of custom level files from the server data
1.  Delete old custom_levels.json
1.  Commit and push file changes (note: test runner will pass)
1.  Merge this feature plus the file-change commits together into finished
is it a bad idea in general to have multiple level files with the same name? Should we raise an exception if this occurs?