> For the complete documentation index, see [llms.txt](https://docs.platform.softwareone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform.softwareone.com/extensions/adobe-vip-marketplace/migration-from-vip.md).

# Migrate from Adobe VIP to VIPM

Migrate from Adobe VIP to Adobe VIP Marketplace.

If you are currently ordering subscriptions through the Adobe Value Incentive Plan (VIP) buying program, we recommend you familiarize yourself with the differences between the Adobe VIP and VIP Marketplace programs. 

These differences will help you understand some changes when you are migrated to the VIP Marketplace. The following table shows the differences:

<table data-search="false"><thead><tr><th>Capability</th><th width="137">Changed?</th><th width="270">VIP Marketplace</th><th>VIP</th></tr></thead><tbody><tr><td>Adding licenses</td><td>Yes</td><td>SoftwareOne Marketplace (recommended)<br>or Adobe Admin Console (see Purchase Authorisations)</td><td>SoftwareOne Order<br>or Adobe Admin Console</td></tr><tr><td>Pay for licenses added through Admin Console</td><td>Yes</td><td>7 days</td><td>30 days</td></tr><tr><td>Returns</td><td>Yes</td><td>14 days after order date. No partial returns, no return exceptions</td><td>14 days after order date. Some partial returns, Some return exceptions</td></tr><tr><td>Renewal</td><td>Yes</td><td>Auto-renewal at anniversary date.<br>You may opt-out of auto-renewal.</td><td>Manual renewal</td></tr><tr><td>Proration</td><td>Yes</td><td>Daily for added licenses against anniversary date</td><td>Monthly</td></tr><tr><td>Invoicing</td><td>Yes</td><td>Single, consolidated invoice per month</td><td>Single invoice per order</td></tr><tr><td>Market segment</td><td>No</td><td>Commercial, Government, and Education</td><td>Commercial, Government, and Education</td></tr><tr><td>Products</td><td>No</td><td>All VIP products including Enterprise</td><td>All VIP products including Enterprise</td></tr><tr><td>Commitment</td><td>No</td><td>1 year, 3 year, or Extended Terms</td><td>1 year, 3 year, or Extended Terms</td></tr><tr><td>Payment term</td><td>No</td><td>Paid upfront</td><td>Paid upfront</td></tr><tr><td>Pricing levels</td><td>No</td><td>Price levels 1 - 4 (Annual term).<br>Price levels 12 - 14 (3 Year Commit).</td><td>Price levels 1 - 4 (Annual term).<br>Price levels 12 - 14 (3 Year Commit).</td></tr><tr><td>License management</td><td>No</td><td>Adobe Admin Console</td><td>Adobe Admin Console</td></tr></tbody></table>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.platform.softwareone.com/extensions/adobe-vip-marketplace/migration-from-vip.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.