Controlled switching plan
Move to Zennvue in seven deliberate days
A validation-first migration path for event businesses. Preserve the source, test a small batch, reconcile active obligations, and cut over only after acceptance.
Source-system starting points
The same controlled CSV-first playbook can start from these common platforms. Export formats change, so inspect the current source export before mapping.
- HoneyBook
- Dubsado
- 17hats
- Bloom
- Studio Ninja
- Pixieset
- The Knot Pro
- WeddingWire
- Zola
- Táve
- Sprout Studio
The seven-day playbook
Each day ends with evidence and an explicit decision to continue. Large or regulated migrations may need a longer window.
- 1
Scope and protect
Choose the records that need to move, assign an owner, and keep a read-only export from the current system.
- 2
Map the data
Match client fields, statuses, tags, dates, and ownership to the Zennvue import template.
- 3
Import clients
Run a small test batch, review errors, then import the validated client list through the tenant-scoped CSV importer.
- 4
Rebuild active work
Prioritize current events, open proposals, unsigned contracts, unpaid invoices, and near-term tasks.
- 5
Configure the studio
Set packages, templates, brand details, team access, payment settings, notifications, and calendar connections.
- 6
Reconcile and test
Compare counts and balances, test client-facing links, and have each role complete its critical workflow.
- 7
Cut over safely
Freeze changes in the old system, import the final delta, retain the source export, and communicate the new workflow.
Cutover gates
Do not turn off the source system because an import returned success. Require record-count, balance, access, link, and workflow evidence.
- Source export retained and readable
- Imported and skipped counts reconciled
- Open balances and due dates reviewed
- Client-facing links tested signed out
- Owner, admin, employee, and client roles tested
- Backup and rollback owner named
Frequently asked questions
- Will Zennvue delete data from my old system?
- No. The process starts from a read-only export. Keep that export and control the old account until reconciliation and acceptance are complete.
- What can I import automatically today?
- The production importer accepts tenant-scoped client CSV data. Active proposals, contracts, invoices, events, and files require review and controlled setup so balances and obligations are not silently changed.
- Can I migrate with no downtime?
- A staged cutover can minimize interruption, but exact timing depends on export quality, record volume, provider access, and customer acceptance. Do not promise zero downtime before a test migration.