Skip to content

New: How We Design Technology - our seven-layer architecture model, explained in full. See the architecture

general

Credit Union Merger? Combining Two Microsoft 365 Environments

11/12/2026

Both boards have approved the merger plan, the member notice is with counsel, and the package is headed to the NCUA. Then your VP of IT asks a question nobody put on the integration timeline: which Microsoft 365 tenant survives, and what happens to the other one? There are two email domains, two sets of accounts, two MFA setups, two retention schedules, and maybe two identity providers.

Members and examiners judge a credit union merger in its first year. Members notice when statements arrive from an unfamiliar address or when the branch staff they know can't find a shared file. Examiners notice gaps in access reviews, retention, and incident response between the two organizations. The technology integration deserves the same planning discipline as the core conversion.

At a glance

  • Settle identity first, then move mail, files, and Teams, so every later step lands on accounts and policies you've already decided.
  • Microsoft's cross-tenant tools move mailboxes and OneDrive with per-user licensing, and they leave a defined list of items for your team to rebuild.
  • Use the merger to retire inherited shortcuts, and record each decision so examiners and the next IT leader can follow it.

Where IT fits in the NCUA merger process

The legal steps sit in 12 CFR Part 708b. A federally insured credit union needs the NCUA's prior written approval to merge. Both boards approve the proposal and prepare a merger plan, which goes to the regional director with the proposed member notice and ballot.

Members of the merging credit union generally receive notice 45 to 90 days before the meeting called to vote, and approval takes a majority of the members who vote. After the merger is completed, the continuing credit union certifies completion to the regional director within 30 days of the effective date.

Counsel and compliance own that process. The IT lesson is in the timing. The legal effective date rarely matches the day every mailbox moves, so plan for a coexistence period when two tenants run side by side under one institution, with clear owners for each.

Merge identity first

Every other system trusts identity. Email, Teams, SharePoint, device management, VPN, and many line-of-business applications decide who gets in based on the directory. Settle that layer before you move content, and the rest of the project has a stable foundation.

Start with an inventory on both sides: user and service accounts, administrator roles, MFA methods, conditional access policies, Intune device enrollment, and every application that signs in through Microsoft Entra ID or another provider. If one credit union runs Okta for single sign-on and the other relies on Entra ID alone, decide deliberately which model the combined institution keeps. Either can work. The choice should come from your requirements, staff skills, and cost, with the reasoning written down.

During coexistence, staff from the merging credit union often need to reach Teams and SharePoint in the continuing tenant before their mailboxes move. Microsoft Entra cross-tenant synchronization can create and maintain B2B collaboration accounts for them automatically. Microsoft is clear that it isn't a migration tool, and each synchronized user needs a Microsoft Entra ID P1 license in the source tenant.

Plan the tenant to tenant migration in waves

Microsoft built cross-tenant mailbox migration for mergers and divestitures. It requires a Cross Tenant User Data Migration license for each user, a one-time fee that also covers OneDrive moves, and migrations fail without it. Setup involves an Entra application, organization relationships between the tenants, and a prepared mail user in the target for every mailbox.

The service moves mail, calendars, contacts, tasks, archives, and recoverable items. Several things stay behind:

  • Mail, calendar, contacts, archives
    • Moves with cross-tenant migration?: Yes
    • What to plan: Batch by department and pilot with IT staff first
  • OneDrive files
    • Moves with cross-tenant migration?: Yes, through a separate process under the same license
    • What to plan: Map owners and sharing before the move
  • Teams chats and meeting links
    • Moves with cross-tenant migration?: No
    • What to plan: Export chats under your retention rules and recreate meetings
  • Microsoft 365 Groups
    • Moves with cross-tenant migration?: No
    • What to plan: Rebuild membership and owners in the continuing tenant
  • Sensitivity labels and signatures
    • Moves with cross-tenant migration?: No
    • What to plan: Recreate them before the first wave moves
  • Mailbox, calendar, and Send on Behalf permissions
    • Moves with cross-tenant migration?: No
    • What to plan: Reapply delegate and shared calendar access after each wave
  • Mailboxes on any hold
    • Moves with cross-tenant migration?: Blocked
    • What to plan: Decide with counsel how those records will be preserved

Two details shape day one for staff. A domain can live in only one tenant at a time, and after a move the source mailbox is deleted from the source tenant. Users may sign in with a new name and will need to rebuild their Outlook profiles, so schedule help desk coverage, short written instructions, and MFA re-registration for each wave.

Carry retention and legal holds across on purpose

Retention policies, litigation holds, and eDiscovery cases don't follow mailboxes on their own, and Microsoft blocks the cross-tenant move of any mailbox on hold. Treat that as a decision point for compliance and counsel. Common answers include keeping the source tenant running in a reduced state until obligations are met, or completing an approved export before releasing a hold.

Build the combined retention schedule and recreate its policies and labels in the continuing tenant before data arrives. Records that land in a tenant without the right policies can be deleted or kept on the wrong schedule, and that kind of gap is hard to explain in an exam.

Member-facing email: domains, DMARC, and what you tell members

Members read your email for statements, notices, and fraud alerts, and a merger announcement gives scammers a believable story. Decide early which domain members will see and when it changes. Keep the retiring domain registered and receiving mail long after cutover, so replies and old bookmarks still reach someone.

Before you change anything in DNS, list every system that sends mail as either credit union: Microsoft 365, the core provider, e-statement and marketing platforms, and loan origination tools. Microsoft's guidance is to set up SPF and DKIM for every sender of a domain before configuring DMARC, then start with a monitoring policy (p=none), move to quarantine, and finish at reject. Microsoft also recommends sending bulk mail from third-party services through a subdomain. Skipping these steps can send real member notices to spam on the day you most need them delivered.

Tell members plainly what will change, what won't, and how to recognize a real message from you. Staff need the same clarity a week earlier, including what to say when a member calls to ask whether an email is legitimate.

Keep the core conversion and incident reporting on their own tracks

The core conversion has its own vendor, test cycles, and cutover weekend. Run it as a separate track with a shared calendar, and keep major identity or mailbox moves off its weekend. Watch the touch points: core sign-in that depends on directory accounts, e-statement delivery, and branch devices that need new enrollment.

Incident reporting doesn't pause for integration. Under the NCUA's rule, a federally insured credit union must notify the agency as soon as possible and no later than 72 hours after it reasonably believes a reportable cyber incident occurred, including one caused by a compromise at a CUSO or cloud provider. Two tenants, temporary administrator accounts, and outside migration help widen the surface for a while. Agree on who watches each environment, who decides whether an event is reportable, and how both teams reach that person on any given day.

Fix inherited shortcuts instead of copying them

Every credit union carries a few shortcuts: a shared administrator account, MFA exceptions for a board member, broad sharing links, an old forwarding rule, accounts for staff who left years ago. A migration tool will faithfully move all of them.

Review each one before it crosses over. Retire what no longer serves a purpose, fix what can be fixed, and document a business owner and review date for any exception you keep. A short decision log covering the surviving tenant, the identity model, the domain plan, retention choices, and each exception gives your board a clear record and gives examiners a straight answer when they ask how the combined environment was built.

Start the integration plan before the member vote

The integration goes smoothest when identity, collaboration, retention, member email, and the core conversion each have an owner and a sequence before the vote. At CTP, we plan tenant consolidations layer by layer, starting with identity, and write down every significant decision along with a back-out plan. Learn more about our Microsoft 365 migration work for financial institutions, or schedule a conversation about your merger timeline.

Sources and further reading

Ask about something important for you.

Curious about our take on an industry or technology topic? Let us know.

Contact Us