Migrating from Another Platform | Getting Started | Crafted Call
Migrating from Another Platform
Gallery OwnersUpdated Jul 16, 2026
Switching to Crafted Call from Submittable, CaFÉ, EntryThingy, ArtCall.org, CallForEntry, spreadsheets, or a homegrown system? Crafted Call supports migration from common exports, but the exact path depends on the source platform, export format, record volume, image access, and data quality.
You do not have to choose between historical submission data and a modern platform. Start with an export from your current system, then preview what can be mapped before anything goes live.
What's included
What can usually be migrated when the source export includes it:
Artist records — names, emails, submission history, and profile data
Submissions and artwork metadata — titles, media, dimensions, prices, and statements
Images or files — when the export includes accessible image URLs or files
Jury results — scores, decisions, or rankings where they are included in the source export
Exhibition records — accepted works and basic exhibition details where available
Some settings, email templates, eligibility logic, and custom workflows may need to be rebuilt manually because each platform exports data differently.
What we need from you
CSV is the easiest starting point. Depending on the platform, useful migration materials may include:
Excel/XLSX exports
JSON or SQL dumps
API access to your current platform (if your current vendor supports it)
Screenshots or PDFs of settings we can rebuild manually, such as custom form fields or email templates
If you're not sure what to export, schedule a migration call and we'll walk you through exactly which buttons to click in your existing platform.
How it works
Confirm scope. Tell us what platform you're on, how many calls and submissions you have, and whether you need active calls, history, or both.
Export your data. Most platforms have CSV or spreadsheet exports. If yours does not, we can help identify the next-best export.
Preview the import. Review field mappings, row counts, and any missing or unmapped data before committing.
Import and verify. Import into Crafted Call, spot-check records, and confirm that the data is usable for your team.
Go live. Publish new calls from Crafted Call once your team is comfortable with the migrated records.
Was this article helpful?
Simple CSV migrations can be quick. Larger migrations, active-call transitions, image transfers, and non-standard exports take longer and should be scoped before promising a date.
Per-platform notes
From Submittable
Use Submittable exports for applicant, submission, and form data where available. Email templates and decision letters are typically rebuilt manually so the artist-facing language stays consistent.
From CaFÉ (CallForEntry)
CaFÉ exports may include entries, artist contact info, and uploaded media depending on your account and export permissions. Jury scores can be preserved when they are included in the export.
From EntryThingy
EntryThingy exports can include submission, artist, and jury data. Preserve jury votes and portfolio data where the export includes enough detail to map them cleanly.
From ArtCall.org
Crafted Call includes an ArtCall import path for standard ArtCall CSV exports. The self-serve preview handles CSV files up to 10 MB and 5,000 rows per import. Larger files, image-heavy migrations, active calls, or non-standard exports should be scoped with support before import.
You'll find the self-serve importer — and a running history of your past imports — in the admin dashboard under Import & Migrate.
From CallForEntry or custom platforms
If you're on a homegrown system or smaller platform, start with whatever structured export you have: database dumps, CSVs, JSON, or a shared spreadsheet. The cleaner the source data, the cleaner the import.
From spreadsheets only
Plenty of galleries run calls via Google Forms and spreadsheets. A well-labeled sheet can often be mapped into Crafted Call calls, artist profiles, and submissions.
What does migration cost?
Migration support is scoped based on complexity. Simple CSV imports and standard onboarding help are often straightforward; custom cleanup, large image transfers, active-call transitions, or highly custom data may need a confirmed scope before work starts. We will tell you what is included before you commit.
