Moving to Flowcode 2 is an exciting step for your enterprise. This article covers everything you need to know about your custom domains when transitioning from Flowcode 1 to Flowcode 2.
1. What You Need to Know
If you have a custom domain active in Flowcode 1, keep these three rules in mind:
⭐ You must create a new subdomain for F2
You cannot reuse your existing Flowcode 1 subdomain for Flowcode 2.
⭐ Do not delete your old settings
Your current DNS records must stay exactly as they are to keep your older codes functional.
⭐ Migrated codes will adopt new domain
While both domains will run in parallel, any individual codes you choose to migrate from Flowcode 1 to Flowcode 2 will automatically adopt your new F2 custom domain.
2. Why It Works This Way
The reason you need a new domain is that each platform points to a different technical destination. A single subdomain cannot point to two different platforms at the same time.
The Flowcode 1 Connection: Your current custom domain is already "busy" pointing to your Flowcode 1 account. This connection is what allows your old codes to find their destination.
The Flowcode 2 Connection: To set up Flowcode 2, you need to point a domain to your new Enterprise account.
If you try to "reassign" your Flowcode 1 domain to Flowcode 2, you have to break the first connection. Once that connection is broken, every code you ever set live in Flowcode 1 will stop working. By creating a new, separate subdomain for Flowcode 2, you allow both systems to work side-by-side. Your old codes keep their existing path, and your new enterprise codes get a fresh one.
3. How to Communicate This to Your Tech Team
If you are not the person who manages your company’s domain settings, you can share the following requirements with your IT or DevOps team:
Key Points for IT
Keep existing records: Do not modify or delete the current CNAME records used for our Flowcode 1 account.
Create New CNAME Record: We need a new CNAME record created for a new subdomain prefix.
Pointing the Records:
F1 (Existing): Points to scan.custom.flowcode.com and page.custom.flowcode.com. Leave these as-is.
F2 (New): The new subdomain must point to: whitelabel.flowsto.com
The Goal: This is a parallel setup to support our transition to the Enterprise platform without disabling our legacy codes.
4. What happens to migrated codes?
If you choose to migrate existing codes from Flowcode 1 to Flowcode 2, please note that these codes will adopt the new Flowcode 2 custom domain. While the physical code will remain the same, the underlying URL structure will transition to your new domain to take advantage of Flowcode 2’s enhanced tracking features and capabilities.