Moving Containers Between Organizations

Containers can be moved between organizations you have access to. This is useful for:

• Onboarding: Moving containers from a personal organization to a team
• Team reorganization: Transferring ownership between departments
• Agency handoffs: Transferring containers to clients

Requirements

To move a container, you must be an Owner or Admin of both:

• The source organization (where the container currently lives)
• The target organization (where you want to move it)

How to Move a Container

1. Open the container you want to move
2. Click the Settings tab
3. Scroll to the Move Container section
4. Select the target organization from the dropdown
5. Click Move Container
6. Confirm the migration in the dialog

MCP URL Changes

Moving a container changes its MCP URL. The organization slug in the URL will change to the new organization’s slug.

Before: https://old-org.mcp.usewire.io/container/{id}/mcp After: https://new-org.mcp.usewire.io/container/{id}/mcp

You’ll need to update any AI tools or integrations using this container.

What Gets Migrated

When you move a container, everything transfers to the new organization:

Component	Migrated
Container metadata	✅ Name, description, settings
All uploaded files	✅ Raw files, processed versions
Generated context	✅ Entries, analysis, schema
Processing artifacts	✅ Analysis, transformed data

OAuth Token Invalidation

Any existing OAuth tokens are automatically invalidated during migration.

This means:

• Users will need to re-authorize access to the container
• Any active AI sessions using the container will need to reconnect
• This ensures the new organization has full control over access

Tip

If you’re migrating during active usage, notify users that they’ll need to reconnect their AI tools after the migration completes.

Migration Process

During migration, the container is temporarily paused to prevent changes. Once the migration completes, the container is automatically unpaused and ready for use in the new organization.

The process typically takes a few seconds, but larger containers with many files may take longer.

Troubleshooting

”Container is currently busy”

This error means another operation is in progress on the container (like file processing or another migration). Wait for the current operation to complete before trying again.

Migration seems stuck

Migrations run as background workflows. If the UI doesn’t update:

1. Refresh the page
2. Check if the container appears in the target organization
3. If the container is in both organizations, the migration may have failed mid-process - contact support

Can’t find target organization

Make sure you have Owner or Admin role in the target organization. Members cannot receive migrated containers.