Package Subscription Migrations - Revision history

Dcowan: corrected false statements about when migrations can occur

2021-07-07T03:49:06Z

corrected false statements about when migrations can occur

Scarpenter: /* Overview */

2018-09-26T00:18:25Z

‎Overview

Scarpenter: /* Set the Date of Migration */

2017-09-07T01:55:28Z

‎Set the Date of Migration

Scarpenter at 05:06, 27 June 2017

2017-06-27T05:06:17Z

Scarpenter at 05:40, 12 May 2017

2017-05-12T05:40:34Z

Scarpenter at 05:39, 12 May 2017

2017-05-12T05:39:11Z

Scarpenter: /* See Also */

2017-05-12T04:56:51Z

‎See Also

Scarpenter: /* Start the Migration */

2017-05-12T03:06:30Z

‎Start the Migration

Scarpenter: /* Start the Migration */

2017-05-12T03:06:16Z

‎Start the Migration

Scarpenter: /* Start the Migration */

2017-05-12T03:01:15Z

‎Start the Migration

@@ Line 97: / Line 97: @@
 = Aborting a Migration =
-Cancellation of a migration is possible provided that the migration is not future-dated. To cancel a future-dated migration:
+Aborting of a migration is possible prior to it being finalised via Services > Manual Provisioning (for semi-manual service types) or where the migration date is in the future. To abort a migration:
 Go to the source package subscription under the customer and click the '''Abort Migration'''
@@ Line 108: / Line 108: @@
 * revert the source subscriptions back to '''Active'''.
-Migrations for active services are not possible.  Use the Cancel Package Subscription function with active services.
+If a migration has completed automatically or been manually finalised, you cannot abort or reverse this action. You will be required to <br/>
 = Troubleshooting Migrations =

@@ Line 1: / Line 1: @@
 {{DISPLAYTITLE: Package Migrations}}
 = Overview =
-A package migration is a type of order that gives end users the ability to transition from one package plan to another package plan within the same [[Service_Types|service type]].
+A package migration is a type of order that gives end users the ability to transition from one package plan to another package plan within the same [https://resources.emersion.com/display/EKB/Service+Types service type].
 To understand migrations, it is a good idea to have an awareness of the related billing objects.
-* Customers order (subscribe to) a [[PackagePlans/PackagePlans|package plan]].
+* Customers order (subscribe to) a [https://resources.emersion.com/display/EKB/Package+Plans package plan].
 * When the order is submitted, an 'instance' of the package plan that the customer subscribes to, is created.
 * This 'instance' is called the customer's ''package subscription''. It binds the package plan with the customer.
 * Customers may subscribe to several package plans, creating a set of package subscriptions for each plan they subscribe to.
-Package migrations work in conjunction with the [[PackagePlans/Contract#Package_Pools|package pool]] that stores the contractual benefits and penalties incurred when customers upgrades, cross-grades or downgrade their plan. This ensures customers are charged the appropriate contract break out fees or discounts as they defined in the [[PackagePlans/Contract|Contract]].
+Package migrations work in conjunction with the [[PackagePlans/Contract#Package_Pools|package pool]] that stores the contractual benefits and penalties incurred when customers upgrades, cross-grades or downgrade their plan. This ensures customers are charged the appropriate contract break out fees or discounts as they defined in the [https://resources.emersion.com/display/EKB/Contracts contract].
-Migrations can be paused at any time and retuned to later. Any infomation saved up until this point will be retained, and other users will be prevented from starting another migration while there is already one in prgress.
+Migrations can be paused at any time and returned to later. Any information saved up until this point will be retained, and other users will be prevented from starting another migration while there is already one in progress.
 To continue with an incomplete migration:

@@ Line 46: / Line 46: @@
 === Set the Date of Migration ===
-Choose when the migration will happen.
+Choose what date the migration will occur.
-'''''! IMPORTANT !''''' Setting a future date will not result in the system automatically processing the migration when the date arrives. Particularly with manual provisioning service types, the processing of the migration still needs to be done by a user.  The date is used only to filter migrations in the [[Semi_Manual_Provisioning|'''Manual Provisioning''']] page.
+'''''! IMPORTANT !''''' Setting a future date for a migration to occur will not result in the system automatically processing the migration when the date arrives. By default, a service type will still require a user to process the migration manually via the [[Semi_Manual_Provisioning|'''Manual Provisioning''']] section of Cumulus. The future date is used by the Manual Provisioning page as a filter so users can see what service activation need to be done on a given date.
-−
 If an agent needs to be assigned to the order, select the agent from the commissions fields (requires [[Agent_Management|Agents]] and [[Commissions|Commissions]])

← Older revision		Revision as of 05:06, 27 June 2017
Line 114:		Line 114:
	* [[Account_Management/Customer_Screen/Package_Subscriptions/Contract\| Customer contracts for package subscriptions]]		* [[Account_Management/Customer_Screen/Package_Subscriptions/Contract\| Customer contracts for package subscriptions]]
	* [[Main Page/Provisioning/Service Type Migrate \| Service Type Migrations]]		* [[Main Page/Provisioning/Service Type Migrate \| Service Type Migrations]]
		+	* [[Data_Import/Package_Migration\|Got a bunch of migrations to do? We have a bulk update tool that may help.]]

@@ Line 70: / Line 70: @@
 * the source subscriptions will remain '''Active'''
 * the destination subscription will be '''Preactive'''.
-The destination subscription will be available to manually via the the [[Semi_Manual_Provisioning|'''Manual Provisioning''']] page if needed by checking the .
+The destination subscription will be available to manually activate via the the [[Semi_Manual_Provisioning|'''Manual Provisioning''']] page.
 == Automatically Provisioned Services ==
@@ Line 81: / Line 81: @@
 === Cancelling Services ===
 # The source subscriptions will be initially placed into the status of '''PendingProvCancel'''.
-# The provisioning sub-system (affectionally called 'Cyclone') initiates the relevant interactions with the carrier.
+# The provisioning sub-system (affectionately called 'Cyclone') initiates the relevant interactions with the carrier.
 # The carrier system tells Emersion when the services are cancelled on the network
 # The subscription statuses will be updated to '''Cancelled'''.
@@ Line 98: / Line 98: @@
 [[file: Pkg-sub-abort-migration.png|1200px|]]
-Users will be asked to confirm the action.  Onve vonfirmed the syustem will:
+Users will be asked to confirm the action.  Once confirmed the system will:
 * remove all preactive subscriptions that have been created
-* revert the source subscriptions back to '''Active'''
+* revert the source subscriptions back to '''Active'''.
 Migrations for active services are not possible.  Use the Cancel Package Subscription function with active services.

@@ Line 11: / Line 11: @@
 Package migrations work in conjunction with the [[PackagePlans/Contract#Package_Pools|package pool]] that stores the contractual benefits and penalties incurred when customers upgrades, cross-grades or downgrade their plan. This ensures customers are charged the appropriate contract break out fees or discounts as they defined in the [[PackagePlans/Contract|Contract]].
-= Start the Migration =
+Migrations can be paused at any time and retuned to later. Any infomation saved up until this point will be retained, and other users will be prevented from starting another migration while there is already one in prgress.
-To commence a package subscription migration, go to the [[Account_Management/Customer_Screen/Package_Subscriptions|'''Customer > Package Subscription''']] screen and press the '''Migrate Package Subscription''' button.
 [[file:Pkg-sub-migrations-start.png|1200px|]]
-To continue with an incomplete migration:
+=== Add Service Types ===
-'''Nav: Service > Migrations'''. The following page will be displayed showing a list of all migrations that have occurred, or are in progress. For those in progress, click the Order ID. The system will take the user to the last page within the migration process where it was saved.
+* remove all preactive subscriptions that have been created
-[[File:Pkg-sub-migrations-main.png|1200px|]]
+Migrations for active services are not possible.  Use the Cancel Package Subscription function with active services.
 = Troubleshooting Migrations =

@@ Line 29: / Line 29: @@
 = See Also =
 * [[Account_Management/Customer_Screen/Package_Subscriptions/Contract| Customer contracts for package subscriptions]]
 * [[Main Page/Provisioning/Service Type Migrate | Service Type Migrations]]