> For the complete documentation index, see [llms.txt](https://help.flycode.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.flycode.com/flycode-vs.-profitwell-paddle-retain/what-you-keep-and-gain-if-you-switch.md).

# What You Keep (and Gain) If You Switch

Switching from ProfitWell Retain to FlyCode: keep Retain's cancellation flows, add FlyCode for payment recovery with a one-click Stripe app install, and what you gain.

Moving payment recovery to FlyCode does not mean giving up everything else Paddle Retain does. This page covers what stays, what changes and how the switch works.

## Do I lose ProfitWell's cancellation flows if I move to FlyCode?

No. Retain's cancellation flows, offers and voluntary churn tooling are independent of its payment recovery, so you can keep using them and plug FlyCode in for failed payment recovery only. FlyCode installs from the Stripe App Marketplace with one click; you then disable Retain's payment recovery (its retries and dunning emails) so the two engines do not act on the same invoices, and leave its cancel-flow features on. Recovered invoices and subscription status updates flow back into Stripe as before, so downstream reporting is unaffected.

## What do I gain?

Higher recovery (25 to 40 percent more failed payments recovered on average), coordinated messaging that stops emailing customers about soft declines that retries will fix, backup payment method charging for hard declines, root-cause analytics on why payments fail, and pricing tied to incremental recovery rather than a share of everything recovered including what Stripe would have recovered anyway. Most merchants complete the switch in under an hour and see the uplift build over the first 6 to 8 weeks as the model tunes to their customers.

## Related

* [Connecting FlyCode to Stripe](https://help.flycode.com/flycode-and-stripe/connecting-flycode-to-stripe)
* [Getting Started](https://help.flycode.com/what-is-flycode/getting-started)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://help.flycode.com/flycode-vs.-profitwell-paddle-retain/what-you-keep-and-gain-if-you-switch.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.