migrate-from-v1

Migrate NanoClaw v1 agent data and configurations into v2 architecture.

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/tharunramagiri/bookoraaagent --skill migrate-from-v1-tharunramagiri
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-from-v1
Source: https://github.com/tharunramagiri/bookoraaagent/tree/main/.claude/skills/migrate-from-v1
Command: npx skills add https://github.com/tharunramagiri/bookoraaagent --skill migrate-from-v1-tharunramagiri

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires tsx.

What problem does it solve?

This skill manages the complex transition from NanoClaw v1 to v2, ensuring that your agent's state, history, and configurations are safely migrated without losing continuity or operational integrity.

Core Features & Use Cases

  • State Migration: Safely ports conversation history, scheduled tasks, and database records from v1 to the v2 architecture.
  • Configuration Reconciliation: Automatically updates container settings and cleans up legacy documentation files to match the new system requirements.
  • Use Case: If you are running a v1 agent and want to upgrade to the latest v2 features, this skill guides you through the post-script verification, owner seeding, and access policy setup to ensure your agent is fully functional in the new environment.

Quick Start

Invoke the migrate-from-v1 skill to finalize your agent migration after running the initial bash migration script.

Frequently Asked Questions about migrate-from-v1

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate my agent configuration and conversation history to a new architecture?

Agent configuration migration to a new architecture requires porting conversation history, scheduled tasks, and database records while updating container settings to maintain operational continuity. This skill automates that state transfer safely.

What do I need to upgrade my agent to the v2 architecture?

Upgrading your agent to the v2 architecture requires access to the legacy v1 installation path and the handoff.json log file to ensure idempotent and safe state transfer during the migration process.

How does database seeding work during an agent upgrade?

Database seeding during an agent upgrade involves safely porting legacy database records into the new v2 architecture and running owner seeding to ensure your agent is fully functional in the new production environment.

Can I preserve conversation continuity when updating my agent configuration?

Conversation continuity is preserved during configuration updates by safely porting existing conversation history and scheduled tasks from the v1 installation into the new v2 architecture without losing operational integrity.

What is the best way to handle configuration reconciliation for a production agent deployment?

Configuration reconciliation for a production agent deployment involves automatically updating container settings and cleaning up legacy documentation files to match the new system requirements after the initial migration script runs.

Why does the agent migration process require a handoff.json log file?

The agent migration process requires the handoff.json log file to ensure idempotent and safe state transfer, preventing duplicate data seeding and verifying that the legacy v1 state transfers correctly to v2.