All articles

How to move from EasyWebinar to WebinarStack (AI-assisted, step by step)

We found no EasyWebinar export that recreates a webinar elsewhere. Here is how to rebuild one in WebinarStack by handing an AI assistant your settings.

Josh Miller

We found no EasyWebinar export that recreates a webinar elsewhere, and no major platform with an importer, so switching means rebuilding. You do not have to click through it: give an AI assistant your EasyWebinar settings, email sequence and CTA timings and it rebuilds the webinar in WebinarStack over our MCP server.

This is for someone who has already decided. The WebinarStack vs EasyWebinar comparison and the cheaper alternatives to EasyWebinar page cover whether to switch. If you are weighing EasyWebinar against EverWebinar instead, see EasyWebinar vs EverWebinar. Keep one fact in mind before you start: WebinarStack runs pre-recorded and just-in-time webinars only. If you use EasyWebinar for live events, this move covers only your automated ones.

Nothing here is an import. WebinarStack does not read your EasyWebinar account. You collect your settings, the assistant recreates them, and you review the result. We found no platform with an export that does this, so it is not a shortfall specific to EasyWebinar. EasyWebinar's support documentation, checked 14 November 2026, describes a clone feature that duplicates a webinar's settings to another EasyWebinar webinar of the same type, live to live, simulive to simulive and evergreen to evergreen. We did not find an export to another platform. If you have one, use it and ignore the collection step below.

What should you collect from EasyWebinar first?

Everything the webinar does that is not the video. Open EasyWebinar in one tab and copy out each item below into a single document; screenshots are fine, and you do not need a clean export, which is the point of using an assistant.

  • The webinar's title and description.
  • The session schedule: fixed dates, recurring times or just-in-time sessions, and how it handles attendee time zones.
  • The registration page copy: headline, subhead, button label and privacy note.
  • The automated email sequence: each message's subject and body, and when it sends relative to the session.
  • The CTA and poll timings: what appears, and the second of the video at which it appears.
  • The replay window: whether a replay runs and for how many days.
  • The offer link the CTAs point to.
  • The video itself.

Write down which emails send because of what the attendee did, not only because of a date. Reminders and follow-ups map onto WebinarStack's before-session and after-session rules. Anything sent on watch time, on a click or on a poll answer maps onto a behaviour trigger, and WebinarStack has 18 of them, more than the platforms we compared in our roundup, so this is where your rebuild can end up better than the original rather than equal to it.

How do you get the video somewhere WebinarStack can play it?

Do this first, because it is the one manual step and a reader who finds it at the end feels misled. There are two routes. If the video is already on YouTube or Vimeo, the URL carries over and you give it to the webinar later. If EasyWebinar hosts the file, upload it to WebinarStack's own video library in the dashboard.

No MCP tool uploads video, so the assistant cannot do this part whichever route you take. WebinarStack's own CDN hosting is available from the Growth plan. On Starter, host the video on YouTube or Vimeo.

How do you connect the MCP server?

Create an API key in the dashboard under AI Tools and point your assistant at https://webinarstack.co/api/mcp with the key as a bearer token. The full steps, the scopes and the safety notes are on the MCP server page, so we will not repeat them here. Give the key write scopes for webinars, sessions, registrations, automations and interactions, or the assistant will be able to read but not build. setup_end_to_end needs all of the first four to run.

What do you say to the assistant?

Paste your collected material and a prompt like the one below, with your own values in the brackets. Tell it which tools to use, so you can check what it did.

Rebuild my EasyWebinar webinar "[title]" in WebinarStack as a draft.

1. Create it with setup_end_to_end: [just-in-time / recurring / fixed dates],
   host time zone [zone], attendee time zones [converted / same time].
   Pass the emails below as the automations list. Do not add the default
   five-email sequence.
2. Set the description and registration page copy from the text below.
3. Set the video provider to [YouTube / Vimeo / my uploaded WebinarStack file]
   with this URL: [url].
4. Create the behaviour-triggered email rules with configure_automation_sequence.
5. Add each poll and CTA with interactions_create, at these seconds: [list].
6. Set the offer and replay window with update_offer_replay_basics.
7. Do not publish. When you are done, run setup_status and tell me what is
   still missing.

[paste your EasyWebinar settings, copy and timings here]

Here is what the assistant does with it, by tool:

  • setup_end_to_end creates the draft and its schedule in one call, and can take branding and your email rules at the same time. It does not set the registration page copy or the video. If you leave out the email rules it applies a default five-email sequence, which is why the prompt says not to.
  • update_core_details and update_registration_page_basics set the title, description and registration page copy.
  • update_video_provider points the webinar at YouTube, Vimeo or a file you uploaded to WebinarStack's library.
  • configure_automation_sequence creates up to 20 rules in one all-or-nothing call. Run it once, on a webinar that does not already have those rules, because it does not check for existing ones.
  • interactions_create places a poll or CTA at a second-level offset, separately for the live session timeline and the replay.
  • update_offer_replay_basics sets the offer and the replay window.

A real list of what the assistant can reach is on the MCP page. Two limits matter here: automations can send email, post a webhook, call an email-platform integration or fire a Meta Conversions API event, and SMS is not available through MCP.

How do you check it before publishing?

Ask the assistant to run setup_status, which reports what is still missing across core details, schedule, registration page, video, offer, replay and test registration. Then create a test registration with create_test_registration, or several with register_test_attendees, and walk the attendee path yourself: the confirmation email, the reminders, the room and the timed offers.

Then publish. The agent cannot do this, and that is deliberate. Publishing happens in the webinar editor in the dashboard, which lists anything still missing before it will let the webinar go live.

What about your registrant list?

It is a separate job. The MCP server creates test registrations only, so it cannot load real contacts. Real lists go in through WebinarStack's REST API, which has a bulk registrations endpoint that takes up to 100 rows per request; moving your registrant list has the script and the error codes. Export your contacts from EasyWebinar before you cancel, and treat loading them as its own step, after the webinar is published.

What does not carry over?

Past analytics and historical attendance stay in EasyWebinar, and they do not move to WebinarStack. Integrations have to be connected again in WebinarStack, because a connection made in one product is not carried to another. Export what you want to keep before you cancel, because vendors differ on how long data stays reachable afterwards.

The broader question of moving between any two platforms is in how to switch webinar platforms. If you decide to go ahead, you can start from the WebinarStack home page.

Sources: EasyWebinar's support documentation on the clone webinar feature, checked 14 November 2026. Third-party migration guidance from Wistia, MEETYOO and webinar.net, checked 14 November 2026.

Frequently asked questions

Can I import my EasyWebinar webinar into WebinarStack?
No. WebinarStack has no importer, and nothing in it reads an EasyWebinar account. We found no EasyWebinar export that recreates a webinar on another platform either: its support documentation, checked 14 November 2026, describes a clone feature that copies settings between EasyWebinar webinars of the same type. Switching means rebuilding, which an AI assistant can do over WebinarStack's MCP server.
What can the AI assistant actually build?
The draft webinar and its schedule, the title and description, the registration page copy, the video provider, behaviour-triggered email rules, polls and CTAs at second-level offsets, and the offer and replay window. It cannot upload video, cannot load real registrants, and cannot publish the webinar. Publishing stays in the dashboard editor deliberately.
Do I have to upload my video again?
Only if EasyWebinar hosts the file. A video already on YouTube or Vimeo carries over as a URL you point the new webinar at. If the file lives in EasyWebinar, download it and upload it to WebinarStack's video library. No MCP tool uploads video, so this step is manual either way. WebinarStack's own CDN hosting starts on the Growth plan; Starter embeds from YouTube or Vimeo.
Does this move my live EasyWebinar events too?
No. WebinarStack runs pre-recorded and just-in-time webinars only, so it takes over the automated half of your EasyWebinar account and nothing else. If you present live, you keep a live platform for that. It is worth settling that before you start rather than after you have rebuilt the funnel.
How do my existing registrants move across?
Through WebinarStack's REST API, as a separate job after the webinar is published. Its bulk registrations endpoint takes up to 100 rows per request and allows partial success, so one bad row does not fail the batch. The MCP server creates test registrations only and cannot load a real contact list. Export your contacts from EasyWebinar before you cancel.

Run this on your own webinar

WebinarStack records your webinar once and runs it every day after that, with follow-up driven by what each attendee actually did.