Skip to content

Cloud <-> self-host export and import #597

Description

@keysersoft

Both directions of this are a reason people do not start.

  • Someone evaluating Cloud wants to know they can leave with their configuration.
  • Someone self-hosting who outgrows it wants to move without re-entering 40 connectors.

Scope

  • Export a workspace: connectors, tool definitions, response mappings, MCP servers, roles, knowledge graph. Secrets excluded by design — the export names each required env var and leaves it blank.
  • Import the same bundle into any instance, reporting which credentials must be supplied.
  • Version-stamped, with a clear error when importing a bundle from a newer version.

This one removes a purchase objection in both directions, which is why it is above several older items.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    help wantedExtra attention is neededroadmapOn the published roadmap; exempt from the stale bot

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions