Vital Communities List Migration: Difference between revisions
UVListsBot (talk | contribs) Rewrite migration process as a clear step-by-step workflow |
UVListsBot (talk | contribs) Add subscriber and administrator guidance and clarify migration schedule |
||
| Line 4: | Line 4: | ||
For help with a migration or a question about a particular list, see [[Contact|Contact UVLists]]. | For help with a migration or a question about a particular list, see [[Contact|Contact UVLists]]. | ||
== What subscribers need to do == | |||
Subscribers do not need to take action to move to the new UVLists list. Unless they unsubscribe from the Vital Communities list before its '''Cutover Date''', their subscription and delivery preference will be transferred. After the move, use the new list address shown on the list’s UVLists page. | |||
== What list administrators need to do == | |||
List administrators should review the list’s public page for accuracy, including its purpose, guidelines, owner-contact address, and joining instructions. The [[Vital Communities List Migration/02-list-administrator-review|administrator review request]] explains what to check and how to submit corrections. | |||
== Migration schedule == | == Migration schedule == | ||
| Line 10: | Line 18: | ||
The status column uses these terms: | The status column uses these terms: | ||
{| class="wikitable" | |||
! Status | |||
! Meaning | |||
|- | |||
| Not migrated | |||
| Migration has not started. | |||
|- | |||
| Signup open | |||
| Existing Vital Communities subscribers have been notified. The new list is available for subscriptions but not yet for posting. | |||
|- | |||
| Migrated | |||
| The list is operating on UVLists, the prior Vital Communities list is closed, and an autoresponse directs senders to the new address. | |||
|- | |||
| Complete | |||
| The prior Vital Communities list has been fully retired. | |||
|} | |||
{| class="wikitable sortable" | {| class="wikitable sortable" | ||
| Line 39: | Line 60: | ||
|- | |- | ||
| grantham@lists.vitalcommunities.org || [[Lists:Grantham]] || October 22, 2026 || October 29, 2026 || Not Migrated | | grantham@lists.vitalcommunities.org || [[Lists:Grantham]] || October 22, 2026 || October 29, 2026 || Not Migrated | ||
|- | |- | ||
| hanover@lists.vitalcommunities.org || [[Lists:Hanover]] || October 22, 2026 || October 29, 2026 || Not Migrated | | hanover@lists.vitalcommunities.org || [[Lists:Hanover]] || October 22, 2026 || October 29, 2026 || Not Migrated | ||
| Line 82: | Line 101: | ||
| vershire@lists.vitalcommunities.org || [[Lists:Vershire]] || October 22, 2026 || October 29, 2026 || Not Migrated | | vershire@lists.vitalcommunities.org || [[Lists:Vershire]] || October 22, 2026 || October 29, 2026 || Not Migrated | ||
|- | |- | ||
| | | windsor@lists.vitalcommunities.org || [[Lists:Windsor]] || October 21, 2026 || October 28, 2026 || Not Migrated | ||
|} | |||
Each linked UVLists list page includes its new address, joining instructions, and local guidelines. | |||
== Not yet scheduled == | |||
{| class="wikitable" | |||
! Vital Communities list | |||
! Planning status | |||
|- | |||
| groton_area@lists.vitalcommunities.org | |||
| New list and schedule to be determined. | |||
|- | |- | ||
| | | west_fairlee@lists.vitalcommunities.org | ||
| New list and schedule to be determined. | |||
|- | |- | ||
| | | west_lebanon@lists.vitalcommunities.org | ||
| New list and schedule to be determined. | |||
|- | |- | ||
| | | west_newbury@lists.vitalcommunities.org | ||
| New list and schedule to be determined. | |||
|- | |- | ||
| | | west_norwich@lists.vitalcommunities.org | ||
| New list and schedule to be determined. | |||
|- | |- | ||
| woodstock@lists.vitalcommunities.org | | | woodstock@lists.vitalcommunities.org | ||
| List page in preparation; schedule to be determined. | |||
|} | |} | ||
== Migration process == | == Migration process == | ||
| Line 100: | Line 137: | ||
# '''Announce the move.''' On the '''Announcement Date''', send the [[Vital Communities List Migration/01-move-announcement|move announcement]] to the existing list. It explains the new list, the opt-out process, and the planned cutover date. | # '''Announce the move.''' On the '''Announcement Date''', send the [[Vital Communities List Migration/01-move-announcement|move announcement]] to the existing list. It explains the new list, the opt-out process, and the planned cutover date. | ||
# '''Review list information and allow opt-out.''' List administrators receive the [[Vital Communities List Migration/02-list-administrator-review|administrator review request]] so they can confirm the public list information. Existing subscribers who do not want to move can unsubscribe from the Vital Communities list before the '''Cutover Date'''. | # '''Review list information and allow opt-out.''' List administrators receive the [[Vital Communities List Migration/02-list-administrator-review|administrator review request]] so they can confirm the public list information. Existing subscribers who do not want to move can unsubscribe from the Vital Communities list before the '''Cutover Date'''. | ||
# '''Cut over the list.''' On the '''Cutover Date''', send the [[Vital Communities List Migration/03-closure-announcement|closure announcement]] to remaining subscribers. Place the previous list in '''moderated mode''' so new posts are not distributed, and enable the [[Vital Communities List Migration/05-old-list-autoresponse|old-list autoresponse]] to direct senders to the new list. | # '''Cut over the list.''' On the '''Cutover Date''', send the [[Vital Communities List Migration/03-closure-announcement|closure announcement]] to remaining subscribers. Place the previous list in '''moderated mode''' so new posts are not distributed, and enable the [[Vital Communities List Migration/05-old-list-autoresponse|old-list autoresponse]] to direct senders to the new list for the period set for that migration. | ||
# '''Transfer subscribers and welcome them.''' Import subscribers who did not opt out, including their delivery preferences. Then send the [[Vital Communities List Migration/04-uvlists-welcome-message|UVLists welcome message]] with information about the list, its moderators, and where to get help. | # '''Transfer subscribers and welcome them.''' Import subscribers who did not opt out, including their delivery preferences. Then send the [[Vital Communities List Migration/04-uvlists-welcome-message|UVLists welcome message]] with information about the list, its moderators, and where to get help. | ||
[[Category:List Migration]] | [[Category:List Migration]] | ||
Revision as of 06:43, 19 October 2026
Overview
As described in News/uvlists-and-vital-communities-reach-an-agreement-regarding-transitions-of-upper-valley-lists, UVLists is documenting the migration of community email lists from Vital Communities to UVLists. This page tracks the planned schedule and process; its subpages provide reusable communications for subscribers and list administrators.
For help with a migration or a question about a particular list, see Contact UVLists.
What subscribers need to do
Subscribers do not need to take action to move to the new UVLists list. Unless they unsubscribe from the Vital Communities list before its Cutover Date, their subscription and delivery preference will be transferred. After the move, use the new list address shown on the list’s UVLists page.
What list administrators need to do
List administrators should review the list’s public page for accuracy, including its purpose, guidelines, owner-contact address, and joining instructions. The administrator review request explains what to check and how to submit corrections.
Migration schedule
The schedule below shows the planned announcement and cutover dates for each list. Dates and status may change as migration work progresses.
The status column uses these terms:
| Status | Meaning |
|---|---|
| Not migrated | Migration has not started. |
| Signup open | Existing Vital Communities subscribers have been notified. The new list is available for subscriptions but not yet for posting. |
| Migrated | The list is operating on UVLists, the prior Vital Communities list is closed, and an autoresponse directs senders to the new address. |
| Complete | The prior Vital Communities list has been fully retired. |
| VC List | UVL List | Announcement Date | Cutover Date | Current Status |
|---|---|---|---|---|
| barnard@lists.vitalcommunities.org | Lists:Barnard | October 20, 2026 | October 27, 2026 | Not Migrated |
| bradford@lists.vitalcommunities.org | Lists:Bradford | October 20, 2026 | October 27, 2026 | Not Migrated |
| bridgewater@lists.vitalcommunities.org | Lists:Bridgewater | October 20, 2026 | October 27, 2026 | Not Migrated |
| brownsville@lists.vitalcommunities.org | Lists:Brownsville | October 21, 2026 | October 28, 2026 | Not Migrated |
| chelsea@lists.vitalcommunities.org | Lists:Chelsea | October 21, 2026 | October 28, 2026 | Not Migrated |
| claremont@lists.vitalcommunities.org | Lists:Claremont | October 21, 2026 | October 28, 2026 | Not Migrated |
| enfield@lists.vitalcommunities.org | Lists:Enfield | October 21, 2026 | October 28, 2026 | Not Migrated |
| fairlee@lists.vitalcommunities.org | Lists:Fairlee | October 20, 2026 | October 27, 2026 | Not Migrated |
| grafton@lists.vitalcommunities.org | Lists:Grafton | October 21, 2026 | October 28, 2026 | Not Migrated |
| grantham@lists.vitalcommunities.org | Lists:Grantham | October 22, 2026 | October 29, 2026 | Not Migrated |
| hanover@lists.vitalcommunities.org | Lists:Hanover | October 22, 2026 | October 29, 2026 | Not Migrated |
| hartford@lists.vitalcommunities.org | Lists:Hartford | October 22, 2026 | October 29, 2026 | Not Migrated |
| haverhill@lists.vitalcommunities.org | Lists:Haverhill | October 22, 2026 | October 29, 2026 | Not Migrated |
| lebanon@lists.vitalcommunities.org | Lists:Lebanon | October 22, 2026 | October 29, 2026 | Not Migrated |
| lyme@lists.vitalcommunities.org | Lists:Lyme | October 23, 2026 | October 30, 2026 | Not Migrated |
| mascoma@lists.vitalcommunities.org | Lists:Mascoma | October 23, 2026 | October 30, 2026 | Not Migrated |
| newbury@lists.vitalcommunities.org | Lists:Newbury | October 23, 2026 | October 30, 2026 | Not Migrated |
| norwich@lists.vitalcommunities.org | Lists:Norwich | October 23, 2026 | October 30, 2026 | Not Migrated |
| orford@lists.vitalcommunities.org | Lists:Orford | October 20, 2026 | October 27, 2026 | Not Migrated |
| piermont@lists.vitalcommunities.org | Lists:Piermont | October 23, 2026 | October 30, 2026 | Not Migrated |
| plainfield@lists.vitalcommunities.org | Lists:Plainfield | October 23, 2026 | October 30, 2026 | Not Migrated |
| pomfret@lists.vitalcommunities.org | Lists:Pomfret | October 23, 2026 | October 30, 2026 | Not Migrated |
| reading@lists.vitalcommunities.org | Lists:Reading | October 23, 2026 | October 30, 2026 | Not Migrated |
| royalton@lists.vitalcommunities.org | Lists:Royalton | October 20, 2026 | October 27, 2026 | Not Migrated |
| ryegate@lists.vitalcommunities.org | Lists:Ryegate | October 20, 2026 | October 27, 2026 | Not Migrated |
| sharon@lists.vitalcommunities.org | Lists:Sharon | October 22, 2026 | October 29, 2026 | Not Migrated |
| strafford@lists.vitalcommunities.org | Lists:Strafford | October 20, 2026 | October 27, 2026 | Not Migrated |
| thetford@lists.vitalcommunities.org | Lists:Thetford | October 21, 2026 | October 28, 2026 | Not Migrated |
| tunbridge@lists.vitalcommunities.org | Lists:Tunbridge | October 21, 2026 | October 28, 2026 | Not Migrated |
| vershire@lists.vitalcommunities.org | Lists:Vershire | October 22, 2026 | October 29, 2026 | Not Migrated |
| windsor@lists.vitalcommunities.org | Lists:Windsor | October 21, 2026 | October 28, 2026 | Not Migrated |
Each linked UVLists list page includes its new address, joining instructions, and local guidelines.
Not yet scheduled
| Vital Communities list | Planning status |
|---|---|
| groton_area@lists.vitalcommunities.org | New list and schedule to be determined. |
| west_fairlee@lists.vitalcommunities.org | New list and schedule to be determined. |
| west_lebanon@lists.vitalcommunities.org | New list and schedule to be determined. |
| west_newbury@lists.vitalcommunities.org | New list and schedule to be determined. |
| west_norwich@lists.vitalcommunities.org | New list and schedule to be determined. |
| woodstock@lists.vitalcommunities.org | List page in preparation; schedule to be determined. |
Migration process
Each list follows this general process. The communication templates should be reviewed and updated with the list’s specific dates, addresses, and contacts before they are sent.
- Announce the move. On the Announcement Date, send the move announcement to the existing list. It explains the new list, the opt-out process, and the planned cutover date.
- Review list information and allow opt-out. List administrators receive the administrator review request so they can confirm the public list information. Existing subscribers who do not want to move can unsubscribe from the Vital Communities list before the Cutover Date.
- Cut over the list. On the Cutover Date, send the closure announcement to remaining subscribers. Place the previous list in moderated mode so new posts are not distributed, and enable the old-list autoresponse to direct senders to the new list for the period set for that migration.
- Transfer subscribers and welcome them. Import subscribers who did not opt out, including their delivery preferences. Then send the UVLists welcome message with information about the list, its moderators, and where to get help.