Difference between revisions of "Package Subscription Migrations"

From Emersion
Jump to: navigation, search
Line 1: Line 1:
== Introduction ==
+
{{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]].
  
Emersion have always provided a '''Migrations''' list that allows you to review both ''Incomplete'' as well as ''Complete'' Orders.
+
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]].
 +
* When the order is submitted, an 'instance' is created of the package plan the customer subscribes .
 +
* 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.
  
Customer feedback has pointed out that this page is incredibly slow as the system will initially retrieve '''ALL''' of your Migrations, both Complete & Incomplete. We have enhanced this page to initially return '''NO''' results at all. We have also provided some ''filters'' to allow you to narrow down your search for Orders.
+
Package migrations work in conjunction with the [[Contract|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]].
  
[[File:Services_Migrations_001.png|400px|thumb|center]]
+
== Unable to Migrate ==
 +
Users may find that they cannot commence a package migration for a customer's subscription. The reasons for this will vary and are listed below.
  
<br style="clear:both" />
+
* the customer is under contract
 +
* the package subscription is not active
 +
* the underlying service subscriptions are not active.
 +
** If there are preactive service subscriptions, abort them.
 +
* package is already part of a migration
 +
* package is already part of a CHOWN
 +
* package is already part of an Upgrade
 +
* the service is awaiting an automated provisioning outcome (automated service types only)
 +
* the user is not authorised to migrate the package.
 +
** the user is not the agent attributed to the sale
 +
** the user does not have permission to act on behalf of the agent when performing a migration.
  
=== Search/Filter Fields ===
+
Users will need to resolve any of the above issues before a package migration can commence.
  
Fairly typical fields have been presented on this page for your convenience. Simply enter part of a Customer account '''Name''', part of a '''Package Name''' (Note: This field is using the <u>Internal Name</u> of the package) or an '''Order Number''' - along with selecting one of the 2 completion status filters and click '''Search''' to narrow the results down to a quick and manageable size. The result listing can also be sorted by Order ID, Package Name, or Customer Name.
+
= Start the Migration =
 +
To commence a package subscription migration, go to the [[Account_Management/Customer_Screen/Package_Subscriptions'''Customer > Package Subscription''']] screen and press the '''Migrate''' button.
  
To continue with an ''Incomplete'' Migration, click the Order ID and system will take you back to the Order page where you left off.
+
To continue with an incomplete migration:
  
::'''NOTE: Initially, when you enter the Migrations page, no results will display. In most circumstances customer will be here because they want to continue an incomplete migration. Simply select the correct status from the drop down filter and click Search to speed up your search results.'''
+
'''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.
  
<br />
+
[[File:Pkg-sub-migrations-main.png|1200px|]]
[[Category:Services]]
 
  
  
 
+
= Troubleshooting Migrations =
== Troubleshooting Migrations ==
 
 
[http://wiki.emersion.com.au/wiki/index.php/Category:Services/Unable_to_see_package_during_migration/#Troubleshooting_unable_to_see_package_during_migration Troubleshooting migrations, unable to see winning Package]
 
[http://wiki.emersion.com.au/wiki/index.php/Category:Services/Unable_to_see_package_during_migration/#Troubleshooting_unable_to_see_package_during_migration Troubleshooting migrations, unable to see winning Package]
  
 
= See Also =
 
= See Also =
 
+
* [[Services/Orders/Troubleshooting_Orders/02|Unable to find the destination package for package migration]]
 +
* [[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]]

Revision as of 11:54, 12 May 2017

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 type.

To understand migrations, it is a good idea to have an awareness of the related billing objects.

  • Customers order (subscribe to) a package plan.
  • When the order is submitted, an 'instance' is created of the package plan the customer subscribes .
  • 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 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 Contract.

Unable to Migrate

Users may find that they cannot commence a package migration for a customer's subscription. The reasons for this will vary and are listed below.

  • the customer is under contract
  • the package subscription is not active
  • the underlying service subscriptions are not active.
    • If there are preactive service subscriptions, abort them.
  • package is already part of a migration
  • package is already part of a CHOWN
  • package is already part of an Upgrade
  • the service is awaiting an automated provisioning outcome (automated service types only)
  • the user is not authorised to migrate the package.
    • the user is not the agent attributed to the sale
    • the user does not have permission to act on behalf of the agent when performing a migration.

Users will need to resolve any of the above issues before a package migration can commence.

Start the Migration

To commence a package subscription migration, go to the [[Account_Management/Customer_Screen/Package_SubscriptionsCustomer > Package Subscription]] screen and press the Migrate button.

To continue with an incomplete migration:

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.

Pkg-sub-migrations-main.png


Troubleshooting Migrations

Troubleshooting migrations, unable to see winning Package

See Also