Skip to main content

Moving from Editor Cloud

AVstudio Editor NG keeps editable project files in a local workspace. Open that workspace in VS Code to design pages, configure connections, test in Live Preview, and track changes in Git.

Check the migration route​

The October 2026 Product Guide, chapter 18, announced a Cloud retirement plan for January 15 and a forthcoming project-export workflow. It did not provide an available export procedure or specify the year beside that date. Treat this as the announcement recorded in that edition; confirm the applicable schedule and export instructions through AVstudio product updates or support before planning a migration.

Version 27.0.29 has no direct Cloud-download/import command in the Command Palette. It does bundle avstudio-import-legacy, an AI-guided conversion workflow for an existing legacy build containing data.js and uploads/. Creating a new NG project does not download Cloud content. Keep editable source whenever available; legacy-build reconstruction requires review and is not a lossless source export.

Prepare the existing project​

  1. Record the current pages, navigation, shared controls, themes, assets, variables, datasources, and required functions.
  2. Record each integration's command and feedback mappings, including joins, datapoints, topics, payloads, and authentication requirements.
  3. Keep the existing source/export and last working delivery archive in a separate backup. Record their versions and intended target devices.
  4. Install NG using Installation and account. Use a separate working folder for the local project.
  5. If you have a legacy build, use the staged conversion below. If you need to obtain a Cloud export first, follow the instructions available to your account and preserve the original download.

Use Project structure to identify the local files. If you are rebuilding a screen manually, start with Your first project, then use subpages and global slots for repeated controls and navigation.

Convert a legacy build in 27.0.29​

The bundled avstudio-import-legacy guide requires Node 18 or later and an extracted legacy build whose data.js defines window.staticdata. Keep the original folder untouched and convert into a separate destination.

  1. Run Generate AVStudio skill to obtain the current bundled skills, preserving any existing custom edits first.
  2. Ask the assistant to read .agents/skills/avstudio-import-legacy/SKILL.md and the current avstudio-guide references.
  3. Run the skill's dependency-free extractor from the workspace, supplying your actual paths:
node .agents/skills/avstudio-import-legacy/scripts/extract-legacy.mjs \
  --src "/path/to/legacy-build" \
  --out "/path/to/converted-workspace"
  1. Read migration-report.json before proceeding. It records converted items, substitutions, missing mappings, errors, and a pageWorklist. Exit code 2 means errors were reported.
  2. Migrate the pages one at a time from _legacy/pages/<Name>.legacy.json digests. The extractor converts media, fonts, connectors, variables, datasources, configuration, and function source, but deliberately does not generate finished .page layouts.
  3. Review each digest's layout hint. Preserve fixed placement for a fixed source; compose responsive containers deliberately rather than copying old editor coordinates. Verify element counts, targets, bindings, and chosen orientation.
  4. Build shared slot pages from _legacy/global-containers.json, resolve every report item, and follow the verification steps below.

The extractor rewrites legacy window.avgatorStudio references to window.avstudio. Legacy-only store/audio calls, per-property modifiers, unsupported controls, orientation differences, and AMX mappings can require manual rework. Functions invoked as actions must write state explicitly when needed; their return value is not an assignment. Keep the report as the migration checklist and compare the finished interface with the original build.

Verify the local result​

Run Run Project Health Check, resolve missing references, and compare the interface with the existing project in Live Preview. Check navigation, overlays, slot visibility, themes, media, and layouts at the intended screen sizes.

Test outgoing commands and incoming feedback independently using the real integration mappings. Then build the required archive and verify it on the target runtime before replacing an existing delivery. Keep the editable local source and a record of the validated release; Source control and project handoff covers that workflow.