# Legacy Nodes Migration

### Migrating Existing Nodes to StarGate

Users who currently hold nodes from the legacy VeChain system—such as Economic Nodes or X Nodes—can upgrade their positions into the Stargate staking framework. Migration transitions these nodes into the **NFT-based staking model**, unlocking new delegation and reward mechanics, and aligning users with the protocol’s long-term vision.

***

### How Migration Works

Migration is a **one-click process** that transforms a legacy node into a Stargate-compliant staking NFT. Here’s how it unfolds:

1. The user logs into Stargate with the wallet holding the legacy node.
2. The system detects eligible nodes and displays a **"Migrate"** CTA.
3. The user must have the required amount of **VET available in the wallet**, as hard staking will replace the legacy soft staking.
4. Once confirmed:
   * The **legacy NFT is burned** and removed from circulation.
   * A **new staking NFT**, corresponding to the same tier, is minted.
   * The VET is **hard staked automatically**, locking the collateral.
   * The user selects a validator, and **delegation begins** automatically from the validator’s next period.

There’s no need to manually restake or initiate delegation after migration—**everything is included in a single seamless operation**.

> **No maturity period applies** to migrated nodes. Users begin earning rewards from the validator’s next active period.

{% hint style="warning" %}
Legacy nodes support on platforms as VeBetter and VeVote will be dropped. All owners of existing nodes are invited to migrate in order to keep benefiting from advantages and perks available in the VeChain ecosystem.
{% endhint %}

***

### Migration Preconditions and Restrictions

To protect staking integrity, a few important conditions must be met before a legacy node can be migrated:

#### Maturity Requirement

* Legacy nodes must have **completed their original lock/maturity period**.
* If the NFT is still maturing under the legacy model, migration is **blocked** until maturity ends.

#### Marketplace and Transfer Restrictions

* **Listed for Sale**: Migration is blocked if the legacy NFT is actively listed on a marketplace. Users must delist the NFT first.
* **Recently Transferred**: If the NFT was transferred to a new wallet within the last 4 hours, migration is temporarily disabled. This cooldown ensures ownership integrity and prevents abuse.

These safeguards ensure a **clean transition** into Stargate and prevent edge cases like double rewards, unverified ownership, or sudden asset flips.

***

### Rationale

These restrictions are in place to protect the integrity of the StarGate migration process and prevent edge cases—such as premature reward resets, overlapping ownership states, or marketplace manipulation—from disrupting staking operations. By enforcing these conditions, the system ensures a smooth and secure upgrade path for all legacy node holders.

***

### What Changes after Migration?

Once migration is complete, users gain access to the full Stargate feature set:

* **NFT-Based Staking**: Your node is now represented by a Stargate staking NFT.
* **Hard Staking**: Your VET is locked directly in the staking contract, not soft staked.
* **Delegation Integration**: You’re now operating under the validator-delegator model, which includes:
  * Validator-linked period
  * Period-based reward generation
  * Auto-renewal logic
* **Claim and Boost Tools**: Access to Stargate's interface for managing delegation, claiming rewards, boosting maturity (if needed for future NFTs), and tracking validator performance.

***

### Impact on Supply

For **X Node holders**, if the new NFT is eventually **burned** (e.g., via unstaking), it results in a **permanent reduction** in the total supply of that tier. The same principle that applied in the legacy system continues under Stargate, maintaining X Node scarcity.

***

> ⚠️ Node holders are encouraged to migrate to **retain access** to VeChain ecosystem benefits moving forward.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.stargate.vechain.org/overview/legacy-nodes-migration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.