Skip to main content

Transfer maps between places

Atlas projects are place-local. Places in the same experience do not automatically share them.

An editable project is not the same thing as generated Workspace.Terrain:

  • ServerStorage.AtlasStudioProjects/<project GUID> contains the graph, settings, and paint masks.
  • Workspace.Terrain contains the built voxel result.
  • Optional legacy height samples live separately in ServerStorage.AtlasStudioHeightmaps.

Transfer one editable project​

  1. Save both source and destination places. Keep a backup of the destination.
  2. In the source place, finish the current edit and let its preview settle so Atlas has captured the graph.
  3. In Explorer, expand ServerStorage → AtlasStudioProjects.
  4. Identify the GUID-named project folder. Its Data StringValue contains the map name; do not select the root Index, which only remembers the active map.
  5. Right-click the GUID folder and use Studio's Save to File model command to create a local .rbxm copy.
  6. If the graph contains Stored Heightmap, also save each referenced child under ServerStorage.AtlasStudioHeightmaps.
  7. Open the destination place. Run Atlas Studio once if necessary so ServerStorage.AtlasStudioProjects exists.
  8. Select that root folder, use Studio's Insert from File command, and insert the saved GUID folder beneath it. Insert legacy heightmap children beneath AtlasStudioHeightmaps, preserving their names.
  9. Restart Studio or reload the plugin so ProjectService reads storage again.
  10. Open Map Explorer, activate the imported map, inspect all preview channels, and save the destination place.
Project ID collisions

Do not insert a project if the destination already contains a folder for the same project ID. Atlas does not merge two copies. Back up the destination, then keep one copy or transfer a duplicate project whose Atlas ID is different.

Build in the destination​

The imported project does not copy generated terrain. Review its world coordinates and bounds, because Center X/Z and Base Y may overlap destination content. When you select Build Terrain, Atlas clears all destination Workspace.Terrain before recreating the map. Publish the destination place after validating the build.

Other transfer cases​

  • Another place in the same experience: follow the same steps; ServerStorage is separate for every place.
  • Another experience: the storage process is identical, provided you can edit both experiences and install the plugin.
  • Whole-place copy: saving or publishing a copy of the entire place carries AtlasStudioProjects and existing Terrain together. No individual import is needed.
  • Graph plus masks: masks are children of the project folder and travel automatically with it.
  • Environment: apply optional Lighting settings separately after activating the imported project.