Data Migration Handoff process diagram

This is a worked example. Wavelength built the diagram below from the description on this page. Nobody drew it by hand.

What was said

The customer exports their data from the legacy system. The CSM validates the file format and checks for errors. If there are errors, the CSM sends it back to the customer to fix and resend. If the file is clean, the solutions engineer maps the fields to the new schema. The engineer runs a test import so the customer can review it. The customer signs off on the test. Once signed off, the migration is scheduled.

The diagram

What is in this flow

• Systems: None.
• People and teams: Customer, CSM, Solutions Engineer.
• Decisions: Errors?.
• Size: 11 steps and 11 connections.

Steps

1. Customer
2. Export Data (Customer)
3. CSM
4. Validate File (CSM)
5. Errors?
6. Fix and Resend (Customer)
7. Solutions Engineer
8. Map Fields (Solutions Engineer)
9. Test Import (Solutions Engineer)
10. Customer Sign-Off (Customer)
11. Migration Scheduled

Mermaid code

Copy this into any Markdown file, GitHub README, or Mermaid Live to render the same flow.

flowchart TD
  n1(Customer)
  n2([Export Data])
  n3(CSM)
  n4[Validate File]
  n5{Errors?}
  n6[Fix and Resend]
  n7(Solutions Engineer)
  n8[Map Fields]
  n9[Test Import]
  n10[Customer Sign-Off]
  n11([Migration Scheduled])
  n1 -->|exports| n2
  n2 -->|sends| n3
  n3 -->|validates| n4
  n4 -->|checks| n5
  n5 -->|Yes| n6
  n6 -->|resends| n2
  n5 -->|No| n7
  n7 -->|maps| n8
  n8 -->|tests| n9
  n9 -->|reviews| n10
  n10 -->|signs off| n11

Map your own process

Describe your version out loud, or paste the transcript of a call. Wavelength draws the flow as you talk, and you can edit it by voice, by prompt, or by hand.

Every new account starts with 7 days of Pro. No card needed.

This example is part of our guide for customer success.

More examples

See all flow diagram examples