Import Subscriptions into Nue

by consolidating all your subscriptions in nue, you can manage and track your customers' lifecycle (e g renewals, upsells, downsells, etc ) in a single place active subscriptions can often be associated with products and services that are no longer available nue will allow you to create products and services that have been discontinued so that imported subscriptions can continue to be renewed this migration is targeted towards active subscriptions, whose end date is greater than today this migration will create an order and a subscription for each row in the template active subscriptions can be imported as bundled subscriptions (e g bundled products), or as individual subscriptions note if extensive and manual effort is required to pull the active subscriptions from contracts or various sources, we recommend using a bpo vendor step 1 create products in nue in this step, you will want to make sure that all products and pricing are created the best practice is to validate in salesforce sandbox first for a handful of subscriptions, so create the products and pricing needed in nue sandbox create all products in nue if the products are no longer sold, make sure to end date the products step 2 prep your data this step is likely going to be the most effort querying for all active subscriptions, identifying the appropriate fields (e g subscription start/end date, quantity, list price, etc ), exporting the data will often take a significant amount of time identify your active subscriptions (subscription end date >= today) create the active subscription list by using the nue subscription import template https //docs google com/spreadsheets/d/1ik 0dzc4bdw5x2gt033bqeuh3twxvgvyjobgnqkyres/edit?usp=sharing ensure that your salesforce sandbox can be used to validate the subscriptions (account ids, product ids, etc all exist in sandbox) step 3 validate in sandbox our best practice is to identify a sample set to test in sandbox this will allow you to see how the import process will work nue team will import the subscriptions into salesforce sandbox the import process will create an order and a subscription for each row on the template customer will validate that the data looks accurate and the orders and subscriptions were created correctly step 4 import to production nue team will import orders and subscriptions in production once the customer confirms that the sandbox validation is complete customer will confirm that orders and subscriptions were created guidelines \# guideline examples/notes 1 only active subscriptions (where subscription end date >= today) will be imported into nue if today is 5/3/22, we will create subscriptions if the end date is 5/3/22 or greater 2 you will want to validate in your salesforce sandbox first this means that any account ids associated with active subscriptions will need to exist in salesforce sandbox make sure the account ids, product ids, etc exist in your sandbox 3 if you are mapping old products to new products for these subscriptions, make sure you associate the correct product id if the subscriptions will be auto renewed on legacy products, make sure those products exist in sandbox you can auto renew on an old product, and prevent these products from being sellable by the sales team this is done easily in nue by end dating the product 4 each active subscription should be a single row on the import file this means that the subscription should not be split into multiple rows, but rather it is a single row with a total price that represents the total amount for the length of the subscription a 36 month subscription, with a 12 month renewal term will have a single row in the import file subscription start date subscription end date 36 month subscription term 12 month renewal term total price for the 36 months 5 note that all ids should be the 18 character case sensitive id , from salesforce, and not the 15 character id for years, salesforce'srecord id was 15 characters case sensitive however, a lot of data stores did not support case sensitive ids so, salesforce ran an algorithm to append 3 characters to make ids case sensitive make sure you get the 18 character id from the url 6 the import will not support product bundles since the bundles can be configured in various configurations, nue can only support individual products each row in the sheet will create a new order and subscription import data note that these fields must exist in the salesforce sandbox environment in order to validate refer to the nue subscription import template https //docs google com/spreadsheets/d/1ik 0dzc4bdw5x2gt033bqeuh3twxvgvyjobgnqkyres/edit?usp=sharing field name description required id the id of the subscription, used when importing subscription bundles this can be any string that is unique in the import file this field is only used when importing a product bundle leave this blank if the subscription is not part of a bundle no parentid the id of the parent subscription when importing subscription bundles this is the id of the parent subscription in the file this field is only used whe importing a product bundle leave this blank if the subscription is not part of a bundle no customerid the account id in salesforce yes productid the product id in salesforce (referring to the nue product) please use the 18 character product id note that the 15 character product id is not case sensitive, so we require the 18 character id yes productoptionid product option id for the child subscription used when importing subscription bundles see this product bundle for more information on product options yes (when parentid is not empty) productoptionquantity product option quantity is used for the child subscription when importing subscription bundles when the child subscription is a "bundled" one, set the productoptionquantity = 1 yes (when parentid is not empty) pricebookid the price book id that the price book entry id is associated with yes pricebookentryid the price book entry id in salesforce (referring to the nue price book entry) this should match the uom id and the currency id yes uomid the uom id in salesforce yes quantity quantity of the product or service yes salesprice the sales price, calculated by total price / subscription term / quantity yes totalprice the total price of this subscription yes totalamount the total amount, which for now is equal to the total price yes termdimension the term dimension of the unit of measure it is either in month or year if not provided, the default value is month no subscriptionterm the subscription term is in month or year yes subscriptionstart date the subscription start date yes subscriptionenddate the subscription end date yes autorenew indicates if the subscription should be auto renewed valid values are true; or false; (make sure it's lower case) the default value is false no renewalterm this is the renewal term the default value is 12 (months) no bundled if the subscription is bundled (included), then set this value to 'true' if the subscription is an 'add on', then set the value to 'false' the default value is 'false' no evergreen indicates if this order or subscription contains an evergreen product by default the value is false if the subscription term is null, or subscription end date is null, the subscription will be considered evergreen, thus this value will be set to true during the import process no billingaccountid this is the billing account id for the order in the case that the billing account is different than the customer account, then you can specify the billing account id in this field no billingtiming the billing timing of the subscription if this field is not specified, the account or system level setting will be used no billingperiod the billing period of the subscription if this field is not specified, the account or system level setting will be used no billcycleday the bill cycle day of the subscription if this field is not specified, the account or system level setting will be used no billcyclestartmonth the bill cycle start month of the subscription if this field is not specified, the account or system level setting will be used no