CLZ Comics (sold on the desktop as Comic Collector) exports your catalog as a delimited text file. VerseDB reads that export as it comes: every column below is recognised by name, so the mapping step is a check rather than a job of work.
Step 1: Export from CLZ#
Mobile: CLZ Comics for iOS and Android#
The mobile app has no CSV export of its own. The export lives in CLZ Cloud:
- In CLZ Comics, open the menu and tap Sync with CLZ Cloud, then Sync Changes.
- On a computer, sign in at cloud.collectorz.com/comics with the same CLZ account.
- Open the menu at the top left and click Export to CSV/TXT.
- Leave every field selected, click Export, and download the file.
Desktop: Comic Collector for Windows and macOS#
- Go to File > Export to > Text…
- Leave every field selected.
- Name the file with BROWSE, then click Export.
Comic Collector on macOS always writes the export as a .txt file. VerseDB accepts .csv, .xlsx and .xls, so rename it to .csv before you upload it.
Export every column. A Collection import reads 18 of them, including the grade, the certification number, the purchase price, the storage box and CLZ's own Core ComicID. A trimmed export leaves those fields blank with no warning.
Step 2: Start the import#
- Open Import / Export in the sidebar, then choose Import.
- Pick the import type. A CLZ export feeds three of them:
- Collection — comics you own, with grades, prices and purchase dates
- Read Status — which issues you've read, and when
- Wishlist — comics you want
- Pick CLZ Comics as the source.
- Choose how duplicates are handled: Skip Duplicates (Keep Existing Data) or Update Duplicates (Overwrite with Import Data).
- Upload the file. VerseDB accepts
.csv,.xlsxand.xlsup to 10 MB.
One import runs at a time. Finish or delete the one in progress before starting another. An uploaded file is kept for 7 days.
Step 3: Check the mapping#
VerseDB fills the mapping in for you from the CLZ column names. On a Collection import these 18 columns map themselves, in the order the export puts them:
| CLZ column | VerseDB field |
|---|---|
| Series | series |
| Issue | issue_number |
| Variant Description | variant_description |
| Publisher | publisher |
| Release Date | release_date |
| Format | format |
| Core ComicID | clz_id |
| Core SeriesID | clz_series_id |
| Full Title | full_title |
| Variant | variant_code |
| Grade | grade_score |
| Grading Company | grading_company |
| Purchase Date | purchased_at |
| Purchase Price | price_paid |
| Signed by | signed_by |
| Slab Certification Number | grading_number |
| Notes | notes |
| Storage Box | storage_location |
A Read Status import maps 11 columns: Series, Issue, Publisher, Release Date, Full Title, Core ComicID, Core SeriesID, Variant, Purchase Date, Read, Read Date. Read decides whether a row counts at all. A comic CLZ marks unread is skipped, not imported, and listed under Skipped in the results. Read Date carries when you read it; where a read comic has none, VerseDB falls back to the purchase date and then the release date. A Wishlist import maps the 8 identifying columns and none of the collection data.
You can export your whole library and run a Read Status import on it. CLZ's Read column does the filtering, so only the comics you marked read in CLZ come across.
Three columns are skipped on purpose:
- Issue No. holds the issue number stripped of its variant letter. Issue carries both ("1B"), so that is the column VerseDB reads.
- Cover Price is the publisher's cover price, not what you paid. Purchase Price is what maps to
price_paid. - Read Date is a Read Status field. On a Collection import there is nowhere to put it, so it is left alone.
Every other column in the export (creators, characters, genre, barcode, tags, loan fields) is left unmapped. Set any of them by hand if you want them in a mapped field, or leave them skipped.
Step 4: Review and import#
- VerseDB matches each row against the database and scores the match.
- Review the matches, fix any that are wrong, and resolve conflicts with rows you already have.
- Start the import. Progress updates live, and the result lists every row that failed.
What VerseDB does with CLZ's quirks#
Variant letters. CLZ records the cover twice, spliced onto the issue number (1B) and again on its own in the Variant column (B). VerseDB reads the Variant column, because it is the one that is only ever the code: CLZ shelves an SDCC ashcan as issue 1Ashcan-A, which is not a shape an issue number splits on cleanly. The issue number is still where the issue itself comes from, so 1B matches issue 1. An export with no Variant column falls back to taking the code off the end of the issue number.
Which cover you get. A code is matched against VerseDB's cover naming, so B finds Cover B and RI finds Cover RI. Codes CLZ invents for its own shelving, like Ashcan-A, have no VerseDB equivalent and match no variant. The comic still imports against the right issue.
Core IDs. Core ComicID and Core SeriesID are CLZ's own catalog identifiers, and they make the next import of the same book match exactly. VerseDB stores them against the issue, variant or series when that record has none, and never takes one off a record that already carries it.
Dates. CLZ writes dates as Oct 09, 2024. VerseDB reads that format directly, so you do not need to reformat anything. An unset CLZ date exports as 0000-00-00; VerseDB drops it and imports the rest of the row.
Prices. $24.99 imports as 24.99. The currency symbol is stripped.
Signatures. A CLZ export has no signed yes/no column, only Signed by. A name in that column marks the copy signed.
Grades. A value in Grade marks the copy graded, so a slabbed book comes in with its grade, its grading company and its certification number together.
Free Comic Book Day. CLZ shelves these as Free Comic Book Day 2025 (Star Wars). VerseDB files the book under the series in the parentheses.
Troubleshooting#
The upload was rejected. Check the extension. Comic Collector on macOS saves a .txt. Rename it to .csv.
A column imported as nothing. Look at it on the mapping screen. Any column set to Skip is ignored, and a CLZ column VerseDB does not recognise starts on Skip. Set it by hand and the import will read it.
The mapping screen says no headers were detected. The first row of the file is data rather than column names. Re-export from CLZ with the header row included.
Strange characters in series names. Re-export from CLZ as UTF-8. VerseDB reads a UTF-8 byte-order mark correctly, and handles a semicolon-delimited export as well as a comma-delimited one.
Something else. Email support with the file attached and we will run the import for you.