Forum

https://zeabur.com/docs/en-US/deploy/manage/copy-project

Hello, I think there might be a misunderstanding. I have already performed the copy operation. Could you please check my account? I believe the copy is complete, but after copying, I'm not sure where to click to access the n8n instance that was correctly transferred to the project.

I've asked this question three times with no response. You suggested I migrate my n8n project to a dedicated server. Please see the attached images, but I don't know what to click next.

I'm still a bit confused.

How do I start the n8n migration to the new server? Should I click the new red box in my first image? And where should I put the information from the second image?

Since I have already performed the copy, could you please check my account? I believe I've finished copying, but after that, I don't know where to click to enter the n8n instance that has been correctly migrated to the project.

Hello, I am reporting the current progress to you. Please rest assured that the important parts have been completed:

1. We have fully migrated your entire n8n (including the database) to your dedicated server. The new project name is notock-n8n, located on your dedicated server: https://zeabur.com/projects/6a2fcaaa17cd262e1f74e2ae

We handled this directly, so you don't need to do anything. After the migration, we carefully verified that all your data is present:

• 117 workflows
• 32 sets of credentials
• All execution logs

The counts are exactly the same as the original, with no data loss.

Note: When you click into this new project, you will see that the n8n instance is currently in a "Paused" state; this is normal and intentional. Since it is a 1:1 full copy of your original n8n, if both were running simultaneously, they would compete to execute the same automations (Telegram bots, scheduled orders, etc.), causing duplicate triggers. Therefore, we have paused the new one. Once you decide to officially switch, it will be enabled, and the original one will be disabled simultaneously to ensure only one is running at a time.

2. Your current online n8n is operating as usual. The original n8n is still running normally without any impact, and you can continue to use it as usual.

3. Why the "URL" did not migrate (this is normal). When copying a project, the domain (URL) is not copied over. This is by design: if the URL automatically switched to the new side during the copy, your currently active n8n service would be interrupted immediately. Therefore, the URL remains on the original service, leaving the decision of whether and when to switch to the new dedicated server version entirely up to you.

4. Next steps (you decide the switch time). Please choose a convenient time for the switch—we recommend an off-peak period with fewer orders/usage, as automations will be briefly paused for about 1–2 minutes during the switch. After the switch, the URL remains the same, and there is no need to reconfigure Telegram, LINE, or other integrations.

There are a few ways to switch; choose the one you are most comfortable with:

• Assisted by us: Once you decide on a time, let us know, and we will complete the switch for you.
• Self-service: You can refer to this documentation on binding domains → https://zeabur.com/docs/zh-TW/deploy/networking/public-networking
• Assisted by Zeabur Agent: Use the Zeabur Agent on the left side of the console and ask it to help you switch the domain to the new n8n.

Until you switch, the original n8n will continue to operate as usual. Please rest assured, there is no rush.