> ## Documentation Index
> Fetch the complete documentation index at: https://summer-18f03259-codex-native-multiplayer-entry.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Move an Existing Project to Summer Engine

> Open an existing upstream-compatible project in Summer Engine, verify it against the current compatibility contract, and continue as a Summer game.

## Move to Summer Engine

Summer Engine is the product you install and use. Its current upstream technical base is
Godot Engine 4.7.2, and Summer follows upstream continuously. That lineage preserves familiar
project formats and editing concepts, but it is not the Summer Engine product version and
does not change the identity of your Summer game.

Check the generated [compatibility reference](/reference/compatibility) before migrating.
It distinguishes measured facts from project-compatibility claims that have not yet been
measured.

## Profile Migration

If you are coming from Godot Engine, the node, scene, resource, and GDScript concepts are
familiar. Summer Engine adds its own AI workflow and product surfaces, so verify plugins,
editor customizations, and export behavior instead of assuming every detail is identical.

## What's the Same

The portable foundation includes:

* **Node and scene concepts** — familiar nodes, properties, and relationships
* **GDScript** — the default creator language in Summer Engine
* **Text scene and resource formats** — `.tscn`, `.tres`, and `.gd`
* **Project configuration** — `project.godot`
* **Asset import metadata** — verify on first open because importers can change upstream

## Zero Lock-in

Summer games use upstream-compatible project formats:

| Format           | Description            |
| ---------------- | ---------------------- |
| `.gd`            | GDScript source (text) |
| `.tscn` / `.scn` | Scene files            |
| `.tres` / `.res` | Resource files         |
| `project.godot`  | Project configuration  |

Summer does not require a proprietary replacement for these files. Keep the project in
version control and review the first Summer Engine import diff before accepting it.

### Team Workflows

Mixed-editor teams can share source formats, but should pin compatible versions and review
generated import metadata:

* a collaborator may open the project in the compatible upstream editor,
* a creator opens the same repository in Summer Engine,
* both commit project files to the same repository,
* the team resolves real file changes through its normal review process.

### Worst Case

Your GDScript, text scenes, resources, and assets remain in documented formats. Opening them
in another compatible editor may require an import pass and will not provide Summer-only AI
or platform surfaces.

## What's Different

Summer Engine adds its own AI-native workflow to the familiar technical foundation:

### AI Chat Panel

* **Location**: Docked on the right side of the editor
* **Purpose**: Natural language interface to modify your project
* **Integration**: Directly connected to the editor's APIs

### Enhanced Workflow

Instead of manually clicking through menus:

1. **Describe what you want** - "Add a player character with movement"
2. **Review the plan** - Summer Engine shows you what it will change
3. **Apply or modify** - Accept changes or ask for adjustments
4. **Undo if needed** - All AI changes use the standard undo system

## Project Compatibility

To try an existing Godot Engine project in Summer Engine:

<AccordionGroup>
  <Accordion icon="folder-open" title="Opening Godot projects">
    1. **File → Open Project** (or use Project Manager)
    2. **Browse to the existing project folder**
    3. **Select project.godot file**
    4. **Click "Open"**

    Summer Engine will automatically index your project files for AI understanding.
  </Accordion>

  <Accordion icon="sync" title="Project indexing">
    When you first open a project, Summer Engine:

    * Scans all scripts, scenes, and assets
    * Builds an understanding of your project structure
    * Enables AI to provide contextual help
    * Takes 30 seconds to 2 minutes depending on project size
  </Accordion>
</AccordionGroup>

## Common Questions

<AccordionGroup>
  <Accordion icon="question" title="Will my Godot plugins work?">
    Pure GDScript addons are the safest case. Native extensions and editor integrations are
    version-sensitive; use [Extending Summer](/extending/overview) before enabling them.
  </Accordion>

  <Accordion icon="question" title="Can I go back to Godot?">
    The source formats are upstream-compatible. Pin the compatible upstream version, commit
    first, and expect an import pass; Summer-only AI and platform surfaces will not be present.
  </Accordion>

  <Accordion icon="question" title="What about version compatibility?">
    The current upstream technical base is 4.7.2. No next upstream version is currently
    claimed. The project minimum is unmeasured, so do not
    replace that fact with a blanket “Godot 4.x” compatibility promise. See
    [Compatibility & upstream](/reference/compatibility).
  </Accordion>
</AccordionGroup>

## Getting Started

Ready to try Summer Engine with your existing project?

<CardGroup cols={2}>
  <Card title="Download Summer Engine" icon="download" href="/essentials/installation">
    Get Summer Engine installed on your system
  </Card>

  <Card title="First Chat" icon="message-square" href="/essentials/first-chat">
    Learn how to use AI assistance effectively
  </Card>

  <Card title="AI Operations" icon="zap" href="/ai-tools/operations">
    Understand what AI can do in your project
  </Card>
</CardGroup>

***

Need help or have questions? Reach out to our founders at [founders@summerengine.com](mailto:founders@summerengine.com) or join our community on [Discord](https://discord.gg/yUpgtxnZky) for fast responses.