Before you start
- HoneyBook owner access
- A new Cygnetree workspace
What HoneyBook can export
HoneyBook documents a contact CSV export, but it does not document one complete project-and-artifact export that can be imported somewhere else. That does not prevent a safe move.
On desktop:
- Open Clients → Contacts.
- Select the three-dot menu and Download spreadsheet. HoneyBook says this CSV includes basic client information such as name, email, phone, address, notes, and creation date.
- Open Reports → Download reports and collect every report available on the current plan for the full required date range. Keep the date range and company profile with each file.
- For each active smart file, use its three-dot menu to print or save the complete file, contract, invoice, service selection, and client responses as PDF where applicable.
- Download reusable library assets and project attachments that need to remain available.
Official references:
Available reports vary by plan. An unavailable paid report is not a reason to upgrade only for migration: use the guided inventory below and record what could not be exported.
When there is no complete export
In Settings → Migration center → HoneyBook, choose Guided manual move. Walk the HoneyBook pipeline and prepare a project inventory with one row per active or archived project:
| Column | What to record |
|---|---|
| Source ID | A stable project identifier or documented URL slug—not a row number |
| Project name | The exact source name |
| Client source ID or email | A contact already present in the contact export |
| Source stage | The exact HoneyBook pipeline stage |
| Event date | YYYY-MM-DD when known |
| Archived | true or false |
Then choose one disposition for every category: import, rebuild, archive, exclude, or unresolved. Cygnetree will not approve cutover while a category is unresolved. This makes a manual move measurable instead of relying on memory or pretending that historical activity was imported.
The safe order of operations
- Export and import contacts. In HoneyBook, choose Clients → Contacts → three-dot menu → Download spreadsheet, then in Cygnetree choose Settings → Migration center → HoneyBook. Resolve duplicate and missing identities before importing projects.
- Preserve the source pipeline. Create a separate import pipeline with every HoneyBook stage spelled exactly as exported. Do not “improve” it during the transfer.
- Record the source inventory. Open Settings → Migration center, select HoneyBook, and enter the people, total project, active project, and archived project counts from the contact export and guided pipeline inventory. These numbers remain separate from Cygnetree's counts so an incomplete move cannot appear complete.
- Import the prepared project inventory. Choose the source pipeline, upload the CSV, and review the proposed mappings for Project ID, Project Name, Client Email, and Stage. Event Date and Archived are optional. Existing source IDs are skipped safely; unknown contacts and stages stay in review rather than being guessed.
- Recreate reusable work. Use the Library and builders for templates, forms, automations, packages, and scheduling. Keep source wording and intended audience beside the recreated item until it is approved.
- Record every disposition. Choose import, rebuild, archive, exclude, or unresolved for every migration area, then use the cutover checklist and notes for source freeze and retention.
- Point new inquiries here. Replace forms and links only after their staging tests pass.
Reconcile before cancelling
Download the reconciliation JSON from the migration center. It contains the entered source inventory, current workspace inventory, project-by-project source identifiers, coverage dispositions, completed cutover checks, freeze date, archive date, and notes. Every source project should be imported, already present, explicitly held for review, or intentionally archived outside Cygnetree.
“Evidence complete” means the recorded counts and all ten checks agree; it is not an automatic cancellation command. Review the file, open and sample the archive, and leave HoneyBook available and read-only through the approved archive period. Do not cancel because a screen “looks close.”
What stays archived
Source IDs and source stages remain attached to imported projects so later lifecycle improvements never erase what HoneyBook contained. Signed source contracts, receipts, and payment evidence should be downloaded and retained as immutable archive files; do not recreate signatures or claim that historical money moved through Stripe.
When scanned object storage is configured, private archive files can live in the workspace Files area without changing the historical record they represent. Otherwise, keep them in a controlled business archive and record the location and retention date in migration notes.