# Policy Continuations



Policy continuations facilitate unsafe policy changes, meaning changes that could result in conflicts with existing policy data.

When a policy continuation is executed for a given policy, a new policy is created with a new product type. The original policy is called a *continued* policy, and the new policy is called a *continuation* policy. This process essentially archives the original policy and avoids the need for unsafe policy changes and configuration versioning.

Continuation policies are constructed using the [Continuation Plugin](./policy-continuations).

Use Cases [#use-cases]

The policy continuations feature is designed to support the following use cases:

* Cancelling and rewriting policies
* Transfering policies between accounts
* Upgrading policies from one product to another
* Flat cancellation
* Updating immutable policy data such as timezone and duration basis
* Avoiding the need for configuration versioning

Configuration [#configuration]

Each <ApiLink name="ProductRef">ProductRef</ApiLink> configuration object contains a `configurationFor` property that can be used to specify which products are continued by a given product.

The following configuration example defines the `StandardAuto` product as the continuation for the `PersonalAuto` and `CommercialAuto` products:

```json
{
	"products": {
		"StandardAuto": {
			"continuationFor": ["PersonalAuto", "CommercialAuto"]
		}
	}
}
```

Execution [#execution]

Once your configuration changes have been [deployed](/configuration/general-topics/deployment), policy continuations can be executed by <ApiLink name="issueTransaction">issuing</ApiLink> a [policy transaction](/features/policy-management/policy-transactions) containing a <ApiLink name="ContinuationChangeInstructionRequest">continuation change instruction</ApiLink> for your target policy.

The continuation policy will be constructed based on the