Migration Awareness and Buy In

## Epic: Migration Awareness and Buy-In

**8 participants tested, March 2026**
**Note:** The pre-migration email (1st email) was updated after testing. Notes
reflect both what was tested and the current state of the updated email.

### Summary
User testing shows that business owners need context and reassurance before being
asked to migrate. Many participants did not understand why migration was happening,
whether it was required, or how urgent it was. This reduced willingness to act and
increased hesitation. Buy-in must come before action.

**Outcome:** Users understand why migration matters before being asked to act.

---

### User Story: Understand why migration is required
**Confidence:** High | **Support Risk:** High

As a business owner
I want to know why I must migrate
So I feel confident doing it

#### Notes
- During testing, participants felt the pre-migration email (1st email) could do
more to explain the value before asking them to act
- The updated pre-migration email (1st email) now explains the change, lists
benefits, and includes a "What can I do now?" section — this addresses the
core ask
- Resistance dropped once the purpose was explained
- Context helped users re-frame migration as reasonable rather than disruptive

#### Evidence
5 out of 8 participants said they wanted more context before being asked to act.
The other 3 showed similar hesitation in their behaviour during the session.
*(Research report Slides 10–11; BCR 001, 003, 004, 005, 008)*

#### Actions
- [x] Send a pre-migration email explaining what migration is and why it is happening
- [x] Clearly describe the value of the new system to business owners
- [x] Confirm messaging answers "why now" before any call to action -- updated 1st email addresses this

---

### User Story: Understand that migration is required and when
**Confidence:** High | **Support Risk:** High

As a business owner
I want to know if migration is required and when the deadline is
So I understand the risk of waiting and can plan accordingly

#### Notes
- During testing, participants questioned whether migration was optional and
expected a clear deadline in the pre-migration email (1st email)
- The updated pre-migration email (1st email) now includes: "After migration,
Corporate Online will no longer be available for managing your business" —
consequence and obligation are now stated clearly
- The migration email (2nd email) has a deadline date field
"Complete your account registration by: {MMM, DD, yyyy}" — confirm this
placeholder is replaced with a real date before any email is sent

> **Consolidation note:** Merges "Know if migration is mandatory" and "Know the
> deadline" — both pointed to the same problem and the same fix.

#### Evidence
4 out of 8 participants were unclear whether migration was mandatory or when they
needed to do it.
*(Research report Slides 11–13; BCR 001, 003, 005, 007)*

#### Actions
- [x] State explicitly whether migration is mandatory -- updated 1st email addresses this
- [x] Clarify consequences of not migrating -- updated 1st email addresses this
- [x] Include a clear due date in the migration email -- 2nd email addresses this
- [x] Confirm the date placeholder {MMM, DD, yyyy} in the migration email (2nd email)
is replaced with a real date before any email is sent
- [x] Align language around obligation and timing across both emails

---

### User Story: See other businesses are migrating
**Confidence:** Med | **Support Risk:** Med

As a business owner
I want to know others are doing this too
So it feels real and expected

#### Notes
- During testing, participants responded positively to community-wide framing
- Migration felt safer when positioned as a shared activity
- "Businesses like to hear about other businesses and get a feeling that the whole
business community is busy and active"
- Neither the updated pre-migration email (1st email) nor the migration email
(2nd email) currently includes any community framing or mention of broader
migration progress

#### Evidence
1 participant raised this unprompted. Others reacted positively when the idea was
introduced but didn't bring it up themselves. Treat as directional, not confirmed.
*(Research report Slides 10–11; BCR 001)*

#### Actions
- [x] Include community framing in the pre-migration email (1st email)
- [x] Reference broader migration activity where appropriate
- [x] Reinforce that migration is already underway

Start by reviewing the updated pre-migration email and the migration email described in the issue, then compare them with Research report Slides 10–13 and the cited BCR findings. Confirm whether the checked actions are reflected in the current email content, including the real deadline value and community framing; the issue does not name implementation files or tests.

Written by the indexing model from the issue text.