What can be done to resolve the "Conflict" error message preventing the switch from the "Core" plan to the "Freelancer" plan in Webflow? Support has been contacted but no response has been received yet. Clearing browser cache and cookies, switching plans from different browsers, and verifying payment details and account settings have already been attempted. Any community members who have encountered and resolved this issue, please provide assistance.

TL;DR
  • Check for overlapping project subscriptions and dependencies.
  • Ensure account collaborations and shared projects comply with plan switch criteria.
  • Confirm design assets, CMS items, and features fit within new plan limits.
  • Verify e-commerce compatibility with new plan's transactions and products.
  • Contact Webflow Support via official social media or community forums.
  • Disable premium features temporarily to facilitate the plan switch.

Encountering a Conflict error when switching plans in Webflow can be frustrating. Since you've already tried several steps, here’s a structured approach to help resolve the issue.

1. Check for Existing Subscriptions

  • Ensure there are no overlapping project subscriptions that might cause a conflict.
  • Consider if the current plan has any associated projects that depend on specific limitations or features.

2. Review Account Collaborations

  • Check if your account is part of any teams or has shared projects that might restrict a plan switch.
  • Make sure that any projects shared with or owned by others comply with the conditions required for changing plans.

3. Examine Design Assets Usage

  • Verify that your design assets or CMS items fit within the limits of the new "Freelancer" plan.
  • Ensure that any active features specific to the "Core" plan aren’t exceeding limits imposed by the "Freelancer" plan.

4. Evaluate E-commerce Connections

  • If you’re using e-commerce, ensure that all transactions and products are compatible with the intended new plan.
  • Check for any pending payments or unresolved orders that could cause issues.

5. Contact Webflow Support via Alternative Channels

  • Attempt reaching Webflow Support through their official social media accounts or community forums for a quicker response.
  • Consider posting your issue on Webflow’s official community platform to see if other users or moderators provide insights.

6. Temporarily Downgrade Features

  • Try disabling certain premium features associated with the "Core" plan before attempting the switch.
  • Temporarily unpublished projects reliant on premium features may help remove conflicts.

Summary

Resolving the Conflict error typically involves investigating subscriptions, collaborations, asset limitations, and e-commerce setups that might affect plan changes. Since you haven’t received a response from support yet despite trying basic solutions, consider leveraging community channels or directly posting on Webflow’s platform for additional help.

Rate this answer

Other Webflow Questions