Ground truth view. Every row from the original spec spreadsheet mapped against live migration status.
N/A = account not in migration scope for that component.
Orange text = discrepancy or flag requiring attention.
CSV spec shows "[email protected]" — the "P" may be a data entry error or a first-name initial. No account or person matching this pattern exists in the migration data. Destination unconfirmed.
N/A = account is not in scope for that migration component (TBU, No Transfer, and Functional accounts are excluded from calendar migration and forwarding setup until a Japan target is confirmed or the account type requires it).
Orange rows = active discrepancy requiring manual resolution before that account's migration can be marked complete.
Migration Overview
5
Components complete
2
Components partial
2
Pending / not started
24
Users in scope
16
Shared drives migrated
✅
Shared Drives
All 16 drives created in vervejapan.com. Files, folders, shortcuts, and members transferred.
Complete
✅
Calendar
Events migrated for all in-scope users. Small number of recurring events skipped (Google API limitation).
Complete
✅
Contacts
22 of 25 contacts migrated. 3 contacts could not be created due to duplicate name records.
Complete
✅
Google Groups
6 Japan groups configured. Members assigned. japan-pr@ has no members — pending Ken direction.
Complete
✅
Connected Apps Audit
179 OAuth tokens documented across 24 users. Migration guide produced per app category.
Complete
⚠️
Email Forwarding
7 of 24 accounts forwarding correctly. 16 accounts have no forwarding configured. 1 account destination mismatch (ebisuhq).
Partial
⚠️
Google Chat
31 spaces inventoried on Coffee domain. Google does not support Chat history migration between domains — new spaces must be created on the Japan domain. Requires client direction on which spaces to carry over.
Partial
🔲
Admin App Email Updates
Slack, Figma, Notion, LayerX, Canva, Zoom, Docusign, Zapier, Miro, tl;dv and others require admin email update before cutover.
Pending
🔲
TBU Accounts
moekotagawa@, taitohirakue@, yuzunatamura@ — Japan email addresses not yet assigned.
Needs input
Shared Drive Migration
16
Drives migrated
397
Files copied
73
Folders created
8
Shortcuts created
0
Errors
All 16 shared drives have been created in the vervejapan.com domain and confirmed present via Admin Console. File content, folder structure, shortcuts, and drive membership have been transferred.
RETAIL drive shortcuts link to OML Inc. drive folders. Shortcuts are functional for ken@ and OML drive members. Non-OML Japan users can access via the shortcut if Ken grants them OML drive access.
Drive Name
Tier
Files
Folders
Shortcuts
Members
Status
10月PAYPAY明細共有
1
13
0
0
1
Migrated
2024/7/23 オールハンズ
1
7
0
0
—
Migrated
発注ファイル 雪ノ下
1
4
0
0
3
Migrated
恵比寿店発注シートまとめ
1
4
0
0
1
Migrated
wholesale 契約書
1
3
0
0
1
Migrated
WS契約書関連
1
3
0
0
3
Migrated
全社共有_DRIVE
1
2
0
0
—
Migrated
wholesale 議事録
1
2
0
0
—
Migrated
発注ファイル 北鎌倉
1
1
0
0
4
Migrated
Roasteryコスト移動
1
1
0
0
—
Migrated
Verve Japan
2
29
5
0
1
Migrated
業務改善助成金
2
39
5
0
—
Migrated
CX_DRIVE
2
175
15
0
5
Migrated
Fender Cafe_DRIVE
3
114
40
0
6
Migrated
RETAIL
0
0
8
8
30
Migrated
無題の共有ドライブ
0
0
0
0
1
Migrated
Tier 0 = empty/membership only. Tier 1 = small document stores. Tier 2 = mid-size operational drives. Tier 3 = large file archive. File counts and member counts sourced from pre-migration drive inventory snapshot. 5 Tier 1 drives (2024/7/23 オールハンズ, 全社共有_DRIVE, wholesale 議事録, Roasteryコスト移動, 業務改善助成金) were not present in the membership snapshot — member counts unavailable. All 16 drives confirmed present in Japan domain.
Personal Drive (My Drive)
23
Users complete
22,669
Files migrated
0
Failures
Personal Drive (My Drive) migration is complete for all 23 in-scope users. All files were transferred to the corresponding Japan account using server-side copy — no files were downloaded locally. The migration script used a resume state file, so multiple runs were safe; files already migrated were skipped on subsequent runs.
File counts reflect all files in each user's My Drive at time of migration, including Google Docs, Sheets, Slides (exported as native Google format), and binary files. Folder structure and sharing permissions were replicated. Permissions pointing to Coffee-domain addresses will need to be updated to Japan addresses post-cutover.
Calendar Migration
24
Users complete
~22,900
Events imported
337
Events skipped (see note)
Calendar migration is complete for all 24 in-scope users. All events that could be imported were imported.
What "skipped" means: Events are intentionally excluded from import when (1) the user had explicitly declined that invite on the Coffee domain — those are not carried forward, or (2) the event has no iCalUID (subscription calendars, system-generated entries, holiday calendars imported from external sources). These are not errors and require no action.
Users with zero skips
Coffee account
Japan account
Events
Status
yukinoshita@
kamakura@
44
Complete
ebisu@
yebisugardenplace@
59
Complete
aoitakatsuki@
aoi.takatsuki@
448
Complete
kita-kamakura@
kitakamakura@
28
Complete
keitaro@
keitaro.takemoto@
141
Complete
masashi@
masashi.yamazaki@
122
Complete
naoeguchi@
nao.eguchi@
27
Complete
hikarusakigawa@
hikaru.sakigawa@
688
Complete
vcrjnewomantakanawa@
newomantakanawa@
2
Complete
shinjuku@
newomanshinjuku@
50
Complete
rin@
rin.fukuyama@
1,144
Complete
roppongi@
roppongi@
83
Complete
ebisuhq@
yebisugardenplace@
3
Complete
sanamiyamura@
sana.miyamura@
544
Complete
taiga.katsuragawa@
taiga.katsuragawa@
141
Complete
yoyogi@
yoyogipark@
93
Complete
Users with skipped events (all complete — skips are declined/no-UID events)
Contacts have been migrated for all users who had addressbook entries. Deduplication was applied — contacts already present in Japan accounts were skipped.
3 contacts failed with "Cannot have more than one person.names per source" — this is a Google People API restriction on contacts with duplicate name fields. Affected contacts: Rikako Tsutsumi ([email protected]), Yoichiro Iwata ([email protected]), and one additional entry. These are saved in the retry queue and can be resolved manually if needed.
Several Coffee-domain contacts referenced unmapped addresses (omotesando@, yuki@, kodai@, yasu@, akiyoshi@) — these accounts were not in the migration scope and were logged as warnings. No data was lost.
Google Groups
6
Japan groups configured
25
Members added
1
Group with no members
All 6 Japan domain Google Groups have been created and populated with Japan-domain member addresses. Group settings (delivery, posting permissions) were carried over from Coffee domain equivalents.
[email protected] has no members. The source Coffee group also had no members at time of migration. Ken or Mark can add members directly via Admin Console.
Email Forwarding
7
Forwarding correct & verified
16
No forwarding configured
1
Destination mismatch
Domain-level routing confirmed empty (verified 2026-05-02 in Admin Console → Apps → Gmail → Default routing). Per-user forwarding settings are authoritative with no domain overrides.
16 accounts have no forwarding set. Google requires the destination address to be verified before mail flows — verification is triggered by the account holder. Two approaches available: per-user setup (each Japan user verifies), or a domain routing rule in Admin Console (no per-user action required). Pending Ken/Mark decision on preferred approach.
Full OAuth token audit completed 2026-05-02. All 24 Coffee domain users have been scanned. A detailed per-user breakdown with migration instructions is available in the separate OAuth report: logs/oauth_tokens_20260502_094611.html
Google Apps Script projects (require re-authorization post-cutover)
ken@ has 8 Apps Script projects. kazuaki@ has 6. These scripts will stop functioning after the Coffee account is deactivated and must be re-authorized under the new Japan account. Scripts should be re-opened in the Japan account's script.google.com and re-authorized before cutover if possible.
Google Chat
21
Named spaces inventoried
10
Direct message threads
0
Spaces created on Japan domain
0
Messages migrated
Google does not provide a supported migration path for Chat history. Google Workspace Migrate — Google's own domain migration tool — does not cover Google Chat. There is no official export API, no cross-domain import endpoint, and no Google-provided tooling to move message history between Workspace domains. Workarounds exist but require extensive custom development and are costly to implement. The standard approach is to create new spaces on the Japan domain and accept that historical threads remain on Coffee accounts while they are still active.
Named spaces inventoried (Coffee domain)
Space name
Type
Members (Japan)
Last activity
Action needed
All About Coffee
Space
8
2026-04-14
Pending direction
VCRJ All
Space
8
2026-04-14
Pending direction
VCRJ カスタマーボイス
Space
8
2026-04-14
Pending direction
VCRJ シフト
Space
8
2026-04-14
Pending direction
VCRJ 事故クレーム
Space
8
2026-04-07
Pending direction
VCRJ デイリーレポート＠恵比寿
Space
1
2026-04-14
Pending direction
VCRJ デイリーレポート＠YGP
Space
1
2026-04-14
Pending direction
VCRJ デイリーレポート＠代々木公園
Space
1
2026-04-14
Pending direction
VCRJ デイリーレポート＠六本木
Space
1
2026-04-14
Pending direction
VCRJ デイリーレポート＠北鎌倉
Space
1
2026-04-14
Pending direction
VCRJ デイリーレポート＠新宿
Space
1
2026-04-14
Pending direction
VCRJ デイリーレポート＠鎌倉
Space
1
2026-04-14
Pending direction
VCRJ デイリーレポート＠高輪ゲートウェイ
Space
1
2026-04-14
Pending direction
VCRJ 共有＠恵比寿
Space
1
2026-04-14
Pending direction
VCRJ 共有@YGP
Space
1
2026-04-14
Pending direction
VCRJ 共有＠代々木公園
Space
1
2026-04-14
Pending direction
VCRJ 共有＠六本木
Space
1
2026-04-14
Pending direction
VCRJ 共有＠北鎌倉
Space
1
2026-04-13
Pending direction
VCRJ 共有＠新宿
Space
1
2026-04-14
Pending direction
VCRJ 共有＠鎌倉
Space
1
2026-04-14
Pending direction
VCRJ 共有＠高輪ゲートウェイ
Space
1
2026-04-14
Pending direction
10 direct message threads also inventoried — DMs auto-reconnect between users on the same domain; no action needed.
Remaining Items
Items below are pending Ken/Mark decision or Japan team action. No data has been lost — all source accounts remain active.
Needs Ken or Mark decision
Item
Detail
Priority
Email forwarding — 16 accounts
16 Coffee accounts have no forwarding to Japan. Two options: per-user setup (Japan users verify) or domain routing rule (Admin Console, no user action). Decision needed before cutover.
moekotagawa@, taitohirakue@, yuzunatamura@ — Japan email addresses not yet assigned. Drive and calendar data not migrated for these users.
Before cutover
Admin app email updates
Slack, Figma, Notion, LayerX, Canva, Zoom, Docusign, Zapier, Miro, tl;dv, Make, TableCheck, Wi2, Soundtrack, Notion Calendar. Admin for each platform updates member email before deactivating Coffee accounts.
Before cutover
Google Chat spaces
Determine which Coffee-domain Chat spaces should be recreated on Japan domain. Japan users need to be invited to new spaces.
Ken direction
japan-pr@ group members
Group exists but has no members. Ken to assign if group is still needed.
Ken direction
RETAIL drive — non-OML member access
Shortcuts in RETAIL drive point to OML Inc. folders. Users who are not OML drive organizers will see shortcuts but cannot open targets. Ken to grant OML access as needed.
Ken direction
Post-cutover (Japan team)
Item
Who
Detail
Apps Script re-authorization
ken@, kazuaki@
Open each script project in Japan account, re-authorize. Scripts will stop working when Coffee account is deactivated.
Device sign-ins
All users with iOS/Android/macOS
Remove old @vervecoffee.com account from device, add new @vervejapan.com account.
User-managed app sign-ins
Individual users
OpenAI, Uber, PayPay, Dropbox, Kahoot, Agoda, Acnestudios, Canon, Lumin PDF, Shopify, Indeed, YouTube TV — users sign in with new account.
Revert sharing allowlist
Mark (Admin Console)
Remove vervecoffee.com from Japan domain's sharing allowlist after Coffee accounts are no longer needed.
Delta sync
Scheduled
Run final delta sync of any files modified after the initial migration date, immediately before cutover.
Deactivate Coffee accounts
Mark (Admin Console)
After confirming all users are operating on Japan accounts. Retain accounts for a transition period to preserve forwarding.
Open Items — Pre-Cutover Checklist
Items are organized by owner and urgency. P0 items block cutover and should be resolved first. P1 items are important but can run in parallel once P0 decisions are made. P2/P3 are post-cutover.
P0 — Immediate (blocking cutover)
Item
Owner
Detail
Fix ebisuhq@ forwarding destination
Admin Console
Currently pointing to [email protected]. Correct destination is [email protected] (already a verified forwarding address — no re-verification needed). Update forwarding rule, confirm with a test send.
Confirm roastery-kamakura target
Ken / Mark
CSV spec shows [email protected] — the "P" may be a data entry error or a first-name initial. No account or person matching this pattern exists in the migration data. Confirm the correct destination before any routing is set up for this account.
Resolve TBU accounts (3 users)
Ken / Mark
moekotagawa@, taitohirakue@, yuzunatamura@ have no Japan email assigned. Decision required: (A) assign Japan address and migrate, (B) keep on Coffee, or (C) terminate. No migration work is possible until this is decided.
Set email forwarding — 15 Coffee accounts
Admin Console
Accounts: aoitakatsuki, hikarusakigawa, kazuaki, keitaro, kento, masashi, miku, naoeguchi, rikako, rin, sanamiyamura, stetsuya, taiga.katsuragawa, yukiko, yoyogi. Two approaches: domain routing rule (faster, no per-user verification) or per-user setup (Japan users click verification email). Decision from Mark needed on approach before this can be completed.
Update Slack — 14 users
Slack Admin (Ken)
Update each user's Slack account email to their Japan address before Coffee accounts are deactivated. If done after deactivation, affected users lose Slack access. Slack Admin panel → Members → Edit each user's email.
Update LayerX — 8 users
LayerX Admin
Update user login emails in LayerX admin to Japan addresses before Coffee account deactivation to avoid locked-out expense approvals.
Update account email in Wire & Wireless admin portal for these 3 users before Coffee account deactivation.
Update Notion — 2 users (ken, taiga)
Notion Admin (Ken)
Update member emails in Notion workspace. Ken also has Notion Calendar as a separate OAuth token — handle both in the same session.
Update Canva — 2 users (miku, naoeguchi)
Canva Admin
Reassign team member emails in Canva Teams. Check whether designs are tied to the Coffee Google login and transfer ownership if so.
Update Zoom — 2 users (ken, stetsuya)
Zoom Admin (Ken)
Update account email in Zoom Admin. If Zoom is SSO-linked to Google, update the SSO attribute mapping. Verify recurring meetings are intact after update.
Update ken's single-user apps (8 apps)
Ken
Docusign, Make, Miro, TableCheck, Zapier, tl;dv, Soundtrack Your Brand, Notion Calendar — all linked to [email protected]. Make and Zapier are highest urgency — active automations break the moment Coffee account is suspended. Update Google Workspace connection module in each and re-authenticate.
P1 — Before cutover (important)
Item
Owner
Detail
Google Chat — decide fate of Coffee-only spaces
Ken / Mark
52 Chat spaces exist only on the Coffee domain. Ken/Mark need to review and decide for each: recreate on Japan domain, export/archive, or abandon. Japan users added to recreated spaces will see new messages only — older Coffee-only history is not transferable.
Run final Drive delta sync
Multipoint
Delta sync script is ready. Run within 24 hours before cutover. Sequence: delta_sync.py → rewrite_perms.py → anon_links.py.
Notify all users of cutover date
Ken / Mark
Once cutover date is set, notify all 24 users with: exact date/time, instruction to sign out of Google on all devices and back in with Japan address, and a list of personal apps each user needs to update (Uber, PayPay, Dropbox, etc.).
Verify 8 cafe location inboxes
Admin
Send a test email to each cafe location address on vervejapan.com and confirm receipt. Confirm delegation or shared access is set up for whoever manages each inbox.
Confirm test email delivery. Verify any invoicing or billing system is updated to use this new address. Set up delegation to appropriate team member.
Contacts retry — 3 users with API failures
Multipoint
shinjuku@ (11 contacts), roppongi@ (4), rikako@ (1) — failed due to duplicate display name in Google Contacts API. Manual recreation or retry with deduplication needed.
P2 / P3 — Post-cutover
Item
Owner
Detail
Re-authorize Apps Scripts
Japan team
26 scripts across 7 users must be re-authorized after Japan accounts are active. Priority: ken (11 scripts), kazuaki (6), rikako (4), others. Open each script in Apps Script editor, run once, approve under Japan account.
Device re-authentication (~18 users)
Japan team
All users sign out of Google on iOS/Android/macOS and sign back in with Japan address. MDM/managed device users should coordinate with IT.
Personal app migrations (OpenAI, Uber, PayPay, Dropbox, etc.)
Individual users
Each user updates personal apps that use Google SSO or Coffee email. Check Google Account → Security → Third-party apps for a full list per user.
Export Chat history for abandoned Coffee spaces
Admin (if Ken/Mark decide)
For any Coffee-only spaces not recreated on Japan domain, export conversation history via Google Takeout or Admin Vault before Coffee account deactivation.
Remove vervecoffee.com from Japan allowlist
Admin Console
Remove vervecoffee.com from the Japan domain's Drive sharing allowlist after a transition period. Premature removal breaks any remaining cross-domain shares. Recommended: 30 days post-cutover.
Suspend Coffee accounts
Mark (Admin Console)
After all users confirm Japan account is working. Suspend (do not delete) to retain data and preserve forwarding during transition. Confirm no active automations or app logins still depend on Coffee addresses first.
Cutover Plan
This tab documents the sequence and known constraints for the Coffee → Japan cutover. Items labeled Ken/Mark require their decision or action. Items labeled Admin require Google Workspace Admin Console access. Items labeled Japan team are executed by end users after cutover.
Last capture of any Drive files modified since last sync. Sequence: delta_sync → rewrite_perms → anon_links.
2️⃣
Verify all 24 accounts have active forwarding
Send a test email to each Coffee address. Confirm arrival at the Japan address. Fix any failures before proceeding.
3️⃣
Spot-check shared drive access
5 users across different roles verify they can open RETAIL, CX_DRIVE, and Fender Cafe drives from their Japan accounts.
4️⃣
Test Japan group routing
Send a test message to each configured Japan group (info@, invoice@, wholesale@) and confirm delivery to all members.
5️⃣
Send "switch now" notification to all users
Ken or Mark sends the go-live message. Users sign out of Coffee account on all devices and sign into Japan account.
6️⃣
Add Japan users to approved Chat spaces
For Chat spaces Ken approved in pre-cutover planning, add Japan account members via Admin Console Space Management.
Known Permanent Limitations
The following items cannot be migrated — they are documented here as accepted constraints, not open work items.
Item
Detail
Google Chat history — Coffee-only spaces
Message history in spaces that exist only on the Coffee domain is not transferable to Japan accounts. Japan users added to these spaces see future messages only. Older history remains accessible as long as Coffee accounts are active.
2 calendar events (recurring wholesale) Closed
yoichiro@ — declined this specific recurring instance. Intentionally excluded by migration logic; correct behavior. kazuaki@ — never responded to the invite (needsAction). June 2023 past event, no practical impact. No action required for either.
3 contacts (duplicate display name)
3 contacts across shinjuku@, roppongi@, and rikako@ failed with a Google API limitation for duplicate names. Can be recreated manually in Google Contacts if needed.
Ken's personal Gmail calendar link
The connection between Ken's personal [email protected] calendar and his work account cannot be replicated by the admin API. Ken must re-subscribe manually in Google Calendar settings (cross-account subscriptions are user-only).
179 OAuth tokens (all users)
All third-party app authorizations made from Coffee accounts will expire when those accounts are deactivated. Each user must re-authorize each app from their Japan account. OAuth tokens are non-transferable by design.
4 externally-owned Shared Drives
The バクラク drive (LayerX-owned) and the サポトレ drive (Sapotore-owned) are outside the Coffee domain's control. Japan users who need access should request it directly from those vendors.
Open Questions — Ken / Mark Decision Needed
Question
Context
TBU accounts — assign, hold, or terminate?
moekotagawa@, taitohirakue@, yuzunatamura@ have no Japan email. No migration work can proceed for these three until a decision is made.
Which Chat spaces should Japan users join?
35 named operational spaces on Coffee have no Japan members. A full space list is available in the Google Chat tab. Ken should review and mark which ones to recreate or open on the Japan domain before cutover.
Chat history archive for abandoned Coffee spaces?
For any spaces being abandoned (not recreated on Japan), should message history be downloaded and stored before Coffee accounts are deactivated?
Not migrated — no Japan-domain users are mapped to this account and no destination exists in user_map.json. Content remains on the Coffee domain. If Ken or Mark identify an owner on vervejapan.com, a separate migration plan can be scoped at that time.
Japan Drive trash (approx. 1,700 files)
Files currently in Japan Drive trash from the migration cleanup are recoverable for 30 days. Confirm date by which trash should be permanently emptied.
vcrjcafe@ — listed as no-transfer but holds a higher-tier license
Spec says no transfer needed. Account has a 1010020025 license (higher tier). Confirm deletion of this account is intentional.