How to Migrate Hosting Projects to 4EVERLAND (Using Fleek as an Example)

Introduction

With the rapid development of decentralized web (Web3) hosting services, 4EVERLAND has emerged as a reliable solution offering seamless deployment and high availability. If you’re currently hosting your project on the other platforms and looking to migrate to 4EVERLAND, this step-by-step tutorial will walk you through two effective migration methods and detail the domain migration process. Both methods are designed to minimize downtime and ensure a smooth transition.

Prerequisites Before Migration

Before initiating the migration, ensure you have completed the following preparations to avoid potential issues:

• A valid 4EVERLAND account. If you don’t have one, sign up via the 4EVERLAND website and complete the wallet connection (supported wallets include MetaMask, Wallet Connect, etc.).
• Access to your existing project dashboard (to retrieve CID).
• GitHub account linked to your existing project (required for Method 2).
• Domain management access (if your project uses a custom domain).
• Backup of your project files (as a precautionary measure to prevent data loss).

Method 1: Migrate via IPFS CID Deployment

This method leverages the IPFS Content Identifier (CID) of your existing project, allowing you to deploy directly to 4EVERLAND without reconfiguring the entire repository. It’s ideal for projects already pinned to IPFS(using Fleek as an example).

Step 1: Retrieve the IPFS CID from Fleek

1. Log in to your Fleek account and navigate to the Sites/Hosting section.
2. Select the project you want to migrate.
3. Look for:
   - The IPFS hash/CID field, or
   - The IPFS gateway URL, which often looks like https://<cid>.ipfs.dweb.link or similar.

Copy the CID (a string like Qm... or bafy...).

Step 2: Deploy via CID on 4EVERLAND

1. Log in to your 4EVERLAND account and go to the Hosting section from the left sidebar.
2. Click New Project and select the Hash Deployment option .
3. Paste your Fleek site’s CID into the CID input field.
4. Enter:
   - a unique Project Name.
   - Choose the target platform for deployment (IPFS, Arweave, Greenfield, Walrus or ICP based on your needs).
5. Confirm and click Deploy.

Method 2: Migrate via GitHub Repository Re-deployment

This method links your original GitHub repository to 4EVERLAND for re-deployment. It’s suitable for projects that require ongoing updates, as it enables automatic deployments when changes are pushed to GitHub.

Step 1: Confirm Your GitHub Repository

Make sure your code is hosted in GitHub:

1. If your existing project is already connected to GitHub, confirm:
   - Repository name (e.g., username/project-name)
   - Branch used for deployment (e.g., main, master, production)
2. If your code only exists locally or in another Git provider:
   - Push it to GitHub first.

Step 2: Link GitHub Repository to 4EVERLAND

1. In your 4EVERLAND account, navigate to Hosting and click New Project.
2. Select the Import Git Repository option and connect your GitHub account (authorize 4EVERLAND to access your repositories if prompted) .
3. From the list of repositories, select the one associated with your existing project.
4. Configure the deployment settings and click Deploy to start the deployment process. 4EVERLAND will clone the repository, run the build command, and deploy the project.
5. After deployment, confirm the project is accessible via the generated 4EVERLAND preview URL.

Domain Migration Instructions

Domain migration is a critical step. The process differs depending on whether your domain is currently unbound or already bound to Fleek (or another platform).

Domain Not Bound to Any Platform

If you haven’t bound a custom domain to your exciting project, follow these steps to bind it to 4EVERLAND:

1. In your 4EVERLAND project dashboard, click View Details and navigate to the Domains tab .
2. Click Add Domain and enter your custom domain (e.g., yourdomain.com).
3. Follow the on-screen instructions to add the required DNS records (A record or CNAME) in your domain registrar’s dashboard (If configuring a CNAME record on Cloudflare, ensure the Cloudflare proxy is disabled).
4. Save the DNS settings and wait for propagation (usually 5–30 minutes, depending on your registrar’s TTL settings).

Domain Already Bound to Fleek

If your domain is currently bound to Fleek, you may encounter domain conflict issues even after deleting the domain from Fleek, which will prevent successful binding to 4EVERLAND. In this case, please directly contact 4EVERLAND support for assistance.

Reach out to 4EVERLAND support via Telegram or Discord and submit a support ticket with the following information:
- The domain name
- Your 4EVERLAND account info
- A brief description of the issue (e.g., “Domain is bound to Fleek and cannot be bound to 4EVERLAND due to conflict”)

Our support team will help resolve the conflict promptly. Once the conflict is resolved, bind the domain to 4EVERLAND following the steps in Scenario 1.

Post-Migration Verification

After completing the migration and domain setup, verify the following to ensure everything works correctly:

• Access the project via the 4EVERLAND preview URL and custom domain to confirm content loads properly.
• Check for broken links, missing assets, or functionality issues (compare with the Fleek-hosted version).
• Verify SSL certification (4EVERLAND automatically issues SSL certificates for custom domains).
• Test automatic deployments (for Method 2) by pushing a small change to GitHub and confirming it updates on 4EVERLAND.

Conclusion

Migrating your project from other platforms to 4EVERLAND is a straightforward process with two flexible methods. The CID deployment method offers a quick fix for IPFS-hosted projects, while the GitHub repository method is ideal for long-term maintenance and automatic updates. By following the domain migration steps and verifying post-deployment, you can ensure a seamless transition to 4EVERLAND’s robust hosting infrastructure.

For additional support, visit the 4EVERLAND Documentation or join our community.