Migrate from Mythric M3

The M3 migration tool in the ARC Portal reads a zipped M3 story and creates an ARC game archive. It converts supported content into a starting point for setup and testing. A successful conversion does not mean the room is ready to run.

Keep your original M3 story and media. Work on a copy while you finish the ARC setup.

Prepare the story

On the computer running M3, find your room’s folder inside M3’s stories folder. Compress the whole story folder into a .zip, keeping its internal structure. Include the story file, images, audio, and video.

Files stored outside that folder may be missing from the ZIP. The preview identifies missing media and lets you supply files for the referenced paths.

Convert and review

1. Open the M3 migration tool in the Portal on a desktop browser and select the ZIP. The converter processes the archive in your browser.
2. Review the summary and Needs your attention notices. Check any missing files and the listed connection requirements.
3. Supply missing media where available, then select Build ARC archive.
4. Download the .arc game and the migration report. Keep the report alongside the original story while you complete the setup.

The converter can bring over ordered objectives, staff notes, text and image hints, included media, supported automation steps, and supported PLC, MQTT, and DMX device definitions. The report explains what was converted, omitted, or left for review.

Import into ARC

Configure the required compatible connections in ARC first. The archive describes connection requirements; it does not configure your physical controllers.

In ARC, open Games → Import game and select the generated .arc file. Do not select the original M3 ZIP or the migration report. Match each required connection to the correct controller in your setup, checking the selected targets before continuing.

If the game ID already exists, choose Bring it in as a copy for a separate migration test. The default may update the existing game. Keep a backup before replacing an existing game.

Finish the setup

Use the report as your checklist. Common work includes:

• Automations: incomplete or incompatible events are kept as disabled drafts when possible. Review their conditions, timing, repeat behavior, and staff buttons before enabling them. Calls between events become Run actions and require an ARC release that supports them; ARC’s enabled-state and repeat rules can change how a call behaves.
• Devices and lighting: pair or select smart-home devices in ARC and reconnect their actions. Rebuild saved lighting scenes and DMX queue behavior such as holds, fades, and recycling where the report flags them.
• Rooms and displays: create and assign the room’s displays, audio channels, and intro playback. M3 layouts and styling do not become finished ARC displays automatically.
• Game flow and reset: check alternate modes, objective visibility, timer conditions, and reset behavior. Recreate any manual reset instructions retained in the report.

These are conversion limits. A feature requiring manual setup may still be available in ARC.

Test the complete room

Check each objective, hint, media cue, device action, and staff control. Then run through the game from start to finish and complete the reset with your staff. Verify that each connection controls the intended hardware and that displays and audio use the correct outputs.

Keep the previous setup available until you have verified the ARC version of the room. If a report item is unclear, contact support with the migration report and a description of the behavior you need to preserve.