Switching
Bring your people and your photos. Leave the busywork.
If you already run a badge office on web-based card software, everything you have is a CSV and a folder of photographs, and Badgewright is built to read both. Nothing is saved until you have seen exactly what will happen.
What comes across, and what does not.
- Your people
- A CSV export, in any column order. Column headers are matched to fields for you, ignoring letter case and punctuation, so "first_name" finds First Name.
- Your photos
- A zip. Files are matched by path, by file name in any letter case, or by the primary key, so "10432.jpg" lands on record 10432 without a photo column at all.
- Your card design
- This one you redraw. Card designs are not portable between card programs — ours do not export in a usable form either — so there is nothing to import. Start from a design bound to your fields and change what you need.
How it goes
An afternoon, not a project.
-
Export what you have
One CSV per dataset from your current software, and your photographs gathered into a zip. If the photos are awkward to get out in bulk, ask their support desk before you start.
-
Pick a starting point
Staff & faculty, Students, Visitors, or blank. The Staff & faculty fields are the usual ones — ID Number, names, title, level, photo, issue and expiration dates — so a typical export lines up without renaming anything.
-
Check the dry run
Upload the CSV and the zip together. You see every record that will be added, updated or skipped, every photo that was matched, and every row with a problem, before a single thing is saved.
-
Redraw the card
Start from a design bound to your fields, move things until it matches what you print today, then print the alignment test card once to set the offset for your printer.
While you decide
Nothing is one-way.
Import into a trial account and run it beside what you have now for as long as you like. Your data does not become ours by arriving here.
- The trial holds up to 10,000 records, so you can bring everyone across before choosing a plan
- We do not ask for a card to start
- Export any dataset back to CSV whenever you want
- The dry run means a bad import is a decision you decline, not a mess you clean up
- Import the same file again to update records rather than duplicate them
Coming from CloudBadging in particular?
The Staff & faculty starting point carries the field names CloudBadging ships with, so its export lines up as it stands. We have also written down how the two products differ, from their public documentation.