Memory Transfer

Transfer, copy, and synchronize memories between agents — with granular filtering, conflict resolution, and scheduling.

Overview

The Memory Transfer page allows administrators to move or copy memories from one agent to another. This is essential when onboarding new agents, consolidating knowledge, replicating expertise, or decommissioning agents while preserving their learned knowledge.

Memory Transfer supports both one-to-one and one-to-many transfers, with full control over which memories are included, how conflicts are handled, and whether metadata is preserved.

How It Works

The transfer process follows these steps:

1. Select Source Agent — Choose the agent whose memories you want to transfer. The system displays memory statistics to help you understand what's available.
2. Apply Filters — Narrow down which memories to include by category, date range, importance level, search query, or tags.
3. Preview — See exactly how many memories match your filters and their breakdown by category before committing.
4. Select Target(s) — Choose one or more agents to receive the memories. You can also select all agents in the organization.
5. Configure Options — Set the transfer mode (copy vs. move), conflict resolution strategy, and metadata preferences.
6. Execute — Confirm and run the transfer. A detailed result summary shows how many memories were transferred, skipped, or had conflicts.

Key Concepts

Transfer Modes

Conflict Detection

A conflict occurs when a memory with the same title and category already exists in the target agent. The system detects this automatically and applies your chosen conflict strategy.

Metadata Preservation

When "Preserve metadata" is enabled, the original memory's metadata fields (timestamps, custom data, source information) are carried over to the target. A transferredFrom field is always added to track the memory's provenance, along with a unique transferId.

Memory Categories

Memories are organized into these categories:

• org_knowledge — Organizational facts and procedures
• interaction_pattern — How the agent interacts with users
• preference — User or system preferences
• correction — Corrections to previous behavior
• skill — Learned capabilities and techniques
• context — Background context and environment info
• reflection — Self-assessment and improvement notes
• session_learning — Insights from specific sessions
• system_notice — System-generated notifications

Transfer Tab

The main Transfer tab is where you configure and execute transfers. It's organized into sequential sections: Source, Filters, Preview, Targets, Options, and Execute.

Source Agent Selection

Select an agent from the dropdown to see their memory statistics, including total memory count and number of active categories. If an agent has no memories, the transfer options will be disabled.

Target Selection

Choose one or more target agents individually, or check "All agents in organization" to transfer to every agent except the source. The system automatically prevents self-transfer.

Filters

Filters let you precisely control which memories are included in the transfer:

Filters are cumulative — all active filters must match for a memory to be included. Use the Preview button to verify your filter results before executing.

Conflict Resolution

When a target agent already has a memory with the same title and category, the conflict strategy determines what happens:

History Tab

The History tab provides a complete audit trail of all past transfers. Each entry shows:

• Date and time of the transfer
• Source agent name
• Target agent(s)
• Transfer mode (copy/move)
• Number of memories transferred, skipped, and conflicts encountered

History is paginated with 20 entries per page. Use the Previous/Next buttons to navigate through older transfer records.

Schedules Tab

Automated transfer schedules allow you to set up recurring memory synchronization between agents. This is useful for maintaining knowledge consistency across teams of agents.

Schedule Types

Creating a Schedule

1. Click "New Schedule" in the Schedules tab
2. Select source and target agents
3. Choose transfer mode and conflict strategy
4. Set the schedule type, time, and day (if weekly)
5. Click "Create" to activate the schedule

Managing Schedules

Active schedules are listed in a table showing source, targets, schedule details, mode, and conflict strategy. Use the delete button to remove a schedule. Deleted schedules stop immediately.

Configuration

Memory Transfer works with the default configuration for most use cases. Advanced options include:

• Org Scope — Transfers automatically use the current organization context. Memories are tagged with the active org ID.
• Metadata Fields — The transferredFrom and transferId fields are always added to transferred memories for traceability.
• Batch Size — Large transfers are processed sequentially to avoid overloading the system. Each memory is transferred individually with conflict checking.

Best Practices

Do

• Preview first — always check the memory count and category breakdown
• Use filters to transfer only relevant memories (e.g., only "skill" memories to a new specialist)
• Keep metadata preserved for audit trails and provenance tracking
• Use schedules for ongoing synchronization instead of repeated manual transfers
• Check the History tab to avoid duplicate transfers

Don't

• Don't use "Move" mode unless you're decommissioning the source agent
• Don't transfer system_notice memories — they're agent-specific
• Don't transfer all categories blindly — interaction_pattern and preference may not apply to other agents
• Don't create overlapping schedules for the same source-target pair

Troubleshooting

"No memories match the given filters"

The source agent has no memories matching your current filter combination. Try broadening the filters: select all categories, remove date range restrictions, or clear the search query.

"Cannot transfer memories to the same agent"

Self-transfer is not allowed. Make sure the source and target agents are different. If using "All in org", the source is automatically excluded.

Transfer shows 0 transferred, all skipped

This means every source memory already exists in the target (by title+category match) and your conflict strategy is "Skip". Try "Overwrite" or "Append" to force the transfer.

Memories not appearing after transfer

Refresh the target agent's memory page. If using org context, make sure you're viewing the correct organization. Check the transfer history for error details.

Large transfer is slow

Transfers process memories sequentially for safety. For very large transfers (1000+ memories), consider using filters to break the transfer into smaller category-based batches.

API Reference

The Memory Transfer feature exposes these API endpoints under /api/engine/memory-transfer/:

Related Pages

• Agent Memory — Managing individual agent memories
• Knowledge Bases — Shared knowledge across the organization
• Agent Overview — Agent configuration and management
• Audit Log — System-wide audit trail including transfers