How to migrate from Zoom to Jitsi Meet

Move from Zoom to self-hosted Jitsi Meet: list meetings, recordings and rooms, download what you keep, set up sign-on and dial-in, re-send every invite.

Start with one workloadThe steps

Written for
The engineer who will do the work
Or run by Pilae
At a fixed price, then operated

In short

  • Nothing in Zoom is imported into Jitsi Meet: recurring invites are re-sent with standing room addresses, recordings are downloaded, and dial-in and room systems are replaced.
  • Zoom’s support documentation says cloud recordings of a user downgraded to a free account are deleted after a grace period, so the ones to keep are downloaded while licences run.
  • Phone dial-in to Jitsi Meet runs through Jigasi, an audio-only SIP gateway, and a SIP account from a telephony provider; Jigasi is a connector, not a SIP server.
  • Jitsi is not on Zoom’s list of third-party meetings a Zoom Room can join, so each meeting room needs a PC running Jitsi Meet, or a SIP video call into the meeting.
On this page (10)

Moving from Zoom to Jitsi Meet is a re-pointing of meetings, not an import. Nothing in Zoom has to be imported, because a meeting is a link and a set of options, not a document. What moves is everything around it: recurring invites in people’s calendars carry Zoom links and are re-sent with Jitsi room addresses, the cloud recordings you must keep are downloaded before the licences end, phone dial-in is replaced through a SIP gateway, and meeting rooms built on Zoom Rooms need another way in. The servers are the quick part; the rooms and the phone numbers take the time. This guide covers the order we run it in, and the places it usually goes wrong.

Why teams move from Zoom to Jitsi Meet

Three reasons come up again and again.

  • Calls routed where you choose. With Jitsi Meet on your own machines, audio and video pass through a videobridge in the location you pick, which routes packets in memory and stores none of them. Recordings are files in your storage, not in a vendor’s cloud.
  • No licence per host. In Zoom, hosts are licensed users, cloud recording needs a Pro or higher plan, and webinars, Zoom Rooms and audio conferencing each have a licence or plan of their own. Jitsi Meet is Apache-2.0, with no paid edition of the self-hosted software and no fee per host.
  • Hosts from your directory, guests by link. Hosts sign in through your identity provider, so a leaver loses the right to open meetings with their directory account. Guests need no account: they open the link in a browser or the Jitsi Meet app and wait until a host lets them in.

What you give up is real. Zoom’s AI Companion, which summarises meetings and divides cloud recordings into chapters, has no counterpart in Jitsi Meet. Webinars with registration, panelists, view-only attendees and Q&A have none either, and Zoom Phone is a phone system, which Jitsi Meet is not. Breakout rooms, polls, a lobby and screen sharing are all there. And someone has to run the bridges, which is the part Pilae takes on.

Step 1: list what depends on Zoom

Zoom’s admin reports and its API give you the inventory. The reports need a Pro, Business, Enterprise or Education account and owner or admin rights; they live in the web portal’s Admin Center, under Reports. Zoom documents them in Getting started with Zoom reporting.

  1. People. Users in the Admin Center lists every account and exports the table as CSV. It tells you who hosts, and whose accounts and licences have to be dealt with before the renewal date.
  2. Recurring meetings. The Upcoming meetings and webinars usage report lists scheduled events for a period, recurring ones included, searchable by host. Tick the option that includes events with no fixed time, or those meetings stay hidden. Through the API, GET /users lists the accounts, and GET /users/{userId}/meetings?type=scheduled lists each host’s unexpired meetings, where type 8 is a recurring meeting with a fixed time and type 3 one with no fixed time.
  3. What actually runs. The Meeting and webinar history report shows which meetings take place. A recurring series nobody has used in months is dropped, not moved.
  4. Recordings. The Cloud Recording usage report shows which meetings were recorded and which files they produced. It is the start of the keep list for step 5.
  5. Dial-in. The Audio Conferencing usage report covers phone participation: use it to find out whether people still join by phone.
  6. Webinars, rooms and phones. Webinars and their registration, every Zoom Room with its hardware, and Zoom Phone if you use it, which is a separate decision from meetings.
  7. Links outside calendars. Personal Meeting ID links in email signatures, on the website, in booking pages, documents and chat channel topics.

Every line ends with an owner and a decision: move, replace or drop.

Step 2: test from the networks your guests use

Before anyone relies on it, try a pilot server from the office, from home, from a phone on mobile data and from a partner’s locked-down network. The details that fail are known in advance.

  • Three people, not two. A call between two people goes peer to peer by default, not through the bridge. Jitsi’s FAQ describes the classic fault: a call works with two participants and fails when a third joins, because media to the bridge is blocked. Every participant, guests included, has to reach the bridge on UDP port 10000.
  • TURN over TLS on 443. Some corporate networks allow only TCP on port 443. A TURN server there relays the media of the people behind them; without it, they join but cannot be seen or heard.
  • Mobile apps. When a meeting works in the browser and not in the iOS or Android app, Jitsi’s FAQ points to a TLS certificate served without its full chain.
  • Browsers and devices. Check the browsers your guests use against the handbook’s list of supported browsers, and the headsets and cameras of the people who will host most.

Step 3: set up sign-on, the lobby and standing rooms

Sign-on for hosts. The Jitsi handbook marks the older secure-domain set-up, where hosts type a username and password, as deprecated, and recommends authentication with JSON Web Tokens. Hosts get a token from your identity provider; guests join through an anonymous domain without one. The handbook documents the set-up with Keycloak, which can broker Microsoft Entra ID, and the jitsi-contrib community publishes an OpenID Connect adapter, under Apache-2.0, that signs hosts in through an OIDC provider while keeping guest access and the wait-for-host screen. That adapter is what Pilae runs.

Guests wait for a host. With the wait-for-host module, guests who open an address before any host see a waiting screen, and with the lobby on, a moderator admits each one. A password set during a meeting is removed when the meeting ends, so the lobby, not a password, is what protects a standing room. A moderator can mute everyone but cannot unmute anyone.

Standing room addresses. A Jitsi room exists while people are in it, and its address is the name after your hostname. Give each recurring meeting, each team and each person who had a Personal Meeting ID a standing address, written without spaces, special characters or umlauts, as the handbook asks, and hard to guess. Keep the list beside the inventory: each Zoom meeting, its owner and its new address.

Zoom Jitsi Meet
Meeting ID and passcode Room address; a password set in a meeting ends with it
Personal Meeting ID A standing room address per person
Recurring meeting The same standing address in every occurrence
Waiting room Wait-for-host screen and lobby
Host, co-host, alternative host Signed-in hosts as moderators
Breakout rooms Breakout rooms
Cloud recording Jibri recording, to storage you choose
Live streaming Jibri live streaming to an RTMP address
Dial-in numbers Jigasi and a SIP account from a telephony provider
Webinar A meeting with a lobby, or a live stream; no registration
Zoom Room A room PC running Jitsi Meet, or a SIP video call
Zoom desktop and mobile apps The browser, the Jitsi Meet desktop app or the mobile apps
Zoom’s calendar add-ins The room address in the invite
AI Companion, Zoom Phone No counterpart

Step 4: replace dial-in, recording and room systems

Dial-in. Jigasi is the project’s SIP gateway, and it carries audio only. It registers with a SIP account, from a telephony provider that holds your numbers, and joins conferences on behalf of callers. Its README is explicit that Jigasi is not a SIP server, only a connector: an incoming call goes to the room named in the call’s Jitsi-Conference-Room header, or to one default room. Letting callers choose a meeting by typing its number takes a SIP server in front that asks for it and sets the header; the jitsi-contrib project’s Jigate does this with FreeSWITCH. The number and PIN shown in a meeting’s invite come from a list of dial-in numbers and a conference mapping service the deployment points at. Callers get new numbers either way, so dial-in is ready before the invites go out in step 6. If the report from step 1 shows nobody dials in, drop it.

Recording and live streaming. Jibri records a meeting by running Chrome on a virtual display and encoding it with ffmpeg. Its README says it is meant for a separate machine and records one meeting at a time, so you need as many Jibri machines as recordings and live streams running at once. Jibri writes each recording to its own disk and then runs a finalize script, the place to move the file to backed-up storage and get it to its owner, so settle that script before the first recorded meeting. Live streaming sends a meeting to an RTMP address, such as a streaming platform or a server of your own. Where policy says recordings are kept centrally, switch off local recording in the browser.

Meeting rooms. Zoom documents which third-party meetings a Zoom Room can join, and Jitsi is not on the list. A room that will hold Jitsi meetings gets a PC with a browser or the Jitsi Meet desktop app, which works with any Jitsi Meet deployment, connected to the room’s camera, speakerphone and screen. Ask each device’s vendor whether it can serve a PC that way once Zoom Rooms is gone. For room systems that accept SIP video calls, Jitsi documents a video SIP gateway: a Jibri set up for SIP calls the room into the meeting from the invite dialog, which needs token sign-in and a directory service of your own that lists the rooms.

Calendars. The simplest invite carries the room address in its location and body, and every calendar handles a link. Jitsi also publishes Jidesha, a Chrome extension for calendar integration with Google Calendar and Office 365, which each installation customises, packages and distributes to its own users. If your teams use Element, Element Web can start the conference calls of its rooms on your Jitsi server through its jitsi.preferred_domain setting.

Step 5: download the recordings you keep

Cloud recordings stay in Zoom until someone takes them out, and Zoom’s support documentation says that once a user is downgraded to a free account, their cloud recordings are scheduled for deletion after a grace period. The download is finished while the licences still run.

  1. Agree the keep list. Start from the Cloud Recording report, and decide with each owner what is kept, for how long and why. Check the account’s automatic deletion setting for cloud recordings as well: if it is on, older recordings may already be due to go.
  2. Download a few by hand. Users find their own under Recordings & Transcripts, Cloud recordings in the web portal, and admins see everyone’s under Recording and Transcript Management. Zoom’s documentation describes downloading each recording from its own page.
  3. Download the rest by script. Zoom’s API lists a user’s cloud recordings with GET /users/{userId}/recordings, which needs a Pro or higher plan and cloud recording enabled, and each file in the response carries a download_url that is fetched with an access token. Without from and to dates, the call returns only the current day, and each call covers a limited range, so a script walks every user from GET /users back through time, range by range, and brings everything down. Name each file after its meeting’s topic, date and host, and put it in storage that is backed up.
  4. Transfer before deleting anyone. When an admin deletes a user under Users, Zoom offers to transfer their scheduled meetings, webinars and cloud recordings to one other licensed user first. Use it for everyone who leaves during the move.

Step 6: re-send every recurring invite

Each recurring meeting on the list from step 1 is re-sent by its owner, from their own calendar, so attendees’ calendars update instead of filling up with a second series.

  1. Edit the whole series. Replace the Zoom link, meeting ID, passcode and dial-in block with the standing room address and, where dial-in is used, the new number and PIN, then send the update to every attendee.
  2. Orphaned series. A series whose organiser has left usually has to be created again by someone else, with the old one cancelled.
  3. External meetings. Add one line for guests: open the link in a browser or the Jitsi Meet app, and wait to be let in.
  4. Personal links. Signatures, the website, booking pages and documents get each person’s standing address in place of their Personal Meeting ID.
  5. Hosts. Show every host how to sign in, admit guests from the lobby, open breakout rooms and start a recording, before their first meeting.

When the list is done, remove Zoom’s calendar add-ins from your Microsoft 365 or Google Workspace tenant, so no new invite picks up a Zoom link.

Step 7: run both, then let Zoom lapse

Zoom and Jitsi Meet run side by side while invites move. Nothing has to be synchronised between them, so the parallel period is about catching what was missed.

The cutover, in order

  1. Pilot: One team holds all its meetings in Jitsi Meet for a full cycle, external guests included.
  2. Internal: Recurring internal meetings move, team by team.
  3. External: Meetings with customers and partners move, with the joining line in each update.
  4. Rooms and phones: Meeting rooms and dial-in switch once the hardware and the numbers have been tested.
  5. Lapse: Zoom stays until its renewal date for anything missed, then the licences end.

Watch the Meeting and webinar history report during the parallel period: a meeting that still takes place on Zoom is an invite that was not re-sent, or a link that is still published somewhere. Before the licences end, check the recordings against the keep list one last time and export the reports you want as a record.

Running Jitsi Meet in production

A meeting stores nothing, but the service has more parts than one container.

  • Signalling and bridges. The web interface, Prosody for signalling and Jicofo, which runs each conference, sit together; Jitsi Videobridge routes the media. The handbook says a single server suits a limited number of concurrent conferences and the bridge is the first limit, so capacity grows by adding bridges.
  • Media ports. UDP 10000 on each bridge, reachable by every participant, and TURN over TLS on 443 for the networks that block UDP.
  • Jibri and Jigasi. Jibri on machines of its own, one per recording or stream at a time. Jigasi, when dial-in is used, with its SIP account and its own media ports.
  • What to back up. Configuration, Prosody’s data and the recordings. Meetings in progress hold nothing to restore.
  • Updates in a quiet window. The web interface, Jicofo and the bridge are upgraded together, and a restart interrupts meetings in progress, so updates wait for a window with no meetings booked.
  • Very large audiences. For audiences beyond one conference, the project describes a visitors mode, still marked as work in progress, where participants past a threshold join as viewers through additional signalling servers and bridges. It is a deployment decision, not a setting.

Pilae operates Jitsi Meet this way: signalling, bridges and TURN from the first day, Jibri on machines of its own, hosts signing in through Keycloak or your identity provider, and configuration, Prosody data and recordings backed up daily, encrypted, to an offsite location in the country your contract names, with on Enterprise a restore test every month recorded in the console. The Pilae Agent tests each upgrade on a copy, waits for your approval and applies it in a window with no meetings booked, draining each bridge first. It runs on your premises or on dedicated machines in Pilae Cloud. Media is the one exception to our private network rule: guests reach the bridge’s media port, or TURN on 443 where their network blocks UDP.

Let Pilae run the move

Pilae runs Zoom to Jitsi Meet migrations at a fixed price: the inventory, the network tests from your guests’ side, sign-on and standing rooms, dial-in through your telephony provider, recording with Jibri, the export of the recordings you keep and the re-sending of recurring invites. Then we operate Jitsi Meet for you under a contract that, from the Business plan, includes a monthly availability commitment with service credits. See migration services for what the fixed price covers, or tell us how your teams meet today and we will scope it.

Questions

Can Jitsi Meet import our Zoom meetings?

No, and nothing needs importing. A Zoom meeting is a link and a set of options, and a Jitsi meeting is a room address that exists while people are in it. What moves is everything around the meetings: recurring invites are re-sent with Jitsi addresses, the recordings you must keep are downloaded from Zoom, and dial-in numbers and meeting room systems are replaced.

What happens to our Zoom cloud recordings?

They stay in Zoom until someone downloads them, and Zoom's support documentation says the cloud recordings of a user downgraded to a free account are deleted after a grace period. Admins see every user's recordings in the web portal, where each is downloaded from its own page; for many, a script lists each user's recordings through Zoom's API and downloads every file. Before deleting a user, an admin can transfer their recordings to another licensed user.

Can a Zoom Room join a Jitsi meeting?

No. Zoom lists the third-party meeting services a Zoom Room can join, and Jitsi is not among them. A room that should join Jitsi meetings needs a PC with a browser or the Jitsi Meet desktop app, driving the room's camera, microphone and screen. Room systems that accept SIP video calls can be called into a meeting through a Jibri set up as a video SIP gateway.

Can people still dial in by phone?

Yes, through Jigasi, the SIP gateway of the Jitsi project, which carries audio only. It registers with a SIP account from a telephony provider that holds your numbers. Jigasi is a connector, not a SIP server: a call lands in the room the call names, or in one default room, so letting callers choose a meeting by number takes a SIP server in front that asks for it.

Is Jitsi Meet open source?

Yes. Jitsi Meet and its server components, Jitsi Videobridge, Jicofo and Jibri, are Apache-2.0, with no paid edition of the self-hosted software. 8x8, which maintains the project, sells a hosted version called Jitsi as a Service, which you do not need when the servers are yours. The Jitsi name is a trademark of 8x8, so your deployment carries your own name.

How long does a Zoom to Jitsi Meet migration take?

It depends on the rooms and the phone numbers more than on the servers: how many recurring meetings need re-sending, whether people still dial in, how many recordings must be kept, and how many meeting rooms run Zoom Rooms. The inventory in step 1 settles all four, and Pilae quotes the move at a fixed price once it is done.

Let us run the move for you

An inventory, a parallel run and a cutover plan, at a fixed price. Then we operate the app.

Start with one workload

  • Go deeperSaaS migrationA fixed-scope migration off Google Workspace, Microsoft 365, Zapier, Airtable and ChatGPT to open-source apps, with a parallel run and a cutover plan.
  • CheckManaged operationsPatching, daily encrypted backups, monitoring and incident response for your open-source apps, under an SLA with an availability commitment of up to 99.9%.