Moover Data Migration Guide Table of Contents Overview 1 Data Migration 2 Deployment Considerations 2 Deployment Sequence Checklist 3 Pre-Deployment 3 Deployment 3 Post-Deployment 4 Objects and Data Types 4 Template Access 7 Schema Organization Selection 8 Data Set Customization 9 Data Set Details 10 Default Data Set Element Values 10 Object-Specific Settings and Composite External IDs 12 Template File Contents 18 Overview The Moover data set templates.zip files contain a collection of data set template files. Data sets in the template files give you a great start towards deploying your configure-price-quote () reference data for. Because every implementation is unique, you need to modify these data sets to accurately reflect your implementation. While Prodly created these data sets Moover Data Migration Guide (last revised 4/9/18) 1
and this document for use with, you are welcome to use them as a conceptual reference for any implementation. This document describes how to import and customize the data sets to meet your specific needs. Importing these data sets from the template files does not alter the Prodly Moover app in any way. Importing creates a series of data set records in Prodly Moover to speed up the initial configuration for migration of the reference data in a typical implementation. Prodly has created and tested these templates with Moover using with the High Tech Demo data. The following versions of the templates are available for composite external ID (CEID) and virtual external ID (VEID): CEID for Spring '18 version 212 VEID for Spring '18 version 212 CEID for Winter '18 version 210 VEID for Winter '18 version 210 CEID for Summer '17 version 208 VEID for Summer '17 version 208 CEID for Winter '17 version 27 Prodly intends to validate future versions as they become available. Data Migration Because of the interrelational nature of data, there are many factors to consider and, in certain cases, you need to deploy data sets in a specific order. For example, temporarily disabling features such as triggers might be necessary to avoid problems during migration. Carefully analyze your data to determine the best approach and sequence of migration events. Deployment Considerations The following list contains factors to consider before migrating your data: Triggers Validation rules Multi-currency version version Prodly Moover version Moover template version Duplicate records in your data Moover Data Migration Guide (last revised 4/9/18) 2
Deployment Sequence Checklist The order in which you prepare your environment and deploy the data sets impacts the success of your migration. For example, you need to migrate data for the Price Book object before migrating data for the Product object because products are part of price books. The exact sequence of events depends on your specific data. The following sequence works well to migrate the data from the High Tech Demo organization using the Moover Winter 18 managed package version 1.128, Spring 18, and Summer 17 version 208.9.4. Pre-Deployment 1. In, ensure you have the same major version of installed in your source and destination organizations. 2. In, ensure that the schemas for all objects you are migrating exactly match in the source and destination organizations. 3. In, to the best of your ability, clean the data in your source and destination organizations to eliminate duplicate records. 4. In, ensure you have a user with a license in both your source and destination organizations, and assign the admin permission set to the user. You use this user account as the connection user in Moover when you create the connections for the migration. 5. In, if using multi-currency in your source organization, ensure multi-currency is turned on in your destination organization, and the currency ISO codes match in your source and destination organizations. Refer to the Enable Multiple Currencies help page for details. 6. In your destination organization, disable triggers by navigating to Setup > Installed Packages > > Configure > Additional Settings, selecting Triggers Disabled, and clicking Save. 7. In your destination organization, on the Price Book tab, ensure Standard Price Book is active. 8. In Moover, import the appropriate template version. 9. In Moover, when using CEID templates, ensure that the default composite external IDs are truly unique for your specific data. Deployment 10. In Moover, deploy the SBQQ Price Book Data Set first, before deploying any other data sets. 11. In Moover, deploy the SBQQ Product Data Set or SBQQ Product - No Bundle Data Set depending on your use case next, before deploying any other data sets. 12. In Moover, deploy the remaining data sets in any order. 13. In Moover, validate your deployment results. Note: If you see errors, check the uniqueness of your composite external IDs. Moover Data Migration Guide (last revised 4/9/18) 3
Post-Deployment 14. In, enable triggers in your destination organization. 15. Enjoy all the free time Moover gives you! Objects and Data Types consists of objects containing reference data (for example, products, and price books), objects containing transaction data (for example, opportunities, and orders), and internal use objects. Transaction and internal use objects are not part of a typical data migration, and thus not part of the Moover data set templates. The following table lists the objects along with their object types, data types, and the release versions in which they appear. The template files consider only objects with checkmarks in the reference data column. Object Object Provider Reference Data Transaction Data Internal Use Only 212 S 18 210 W 18 208 S 17 27 W 17 Account Additional Document Asset Attribute Item Attribute Set Attribute Value Block Price Configuration Attribute Configuration Rule Contract Moover Data Migration Guide (last revised 4/9/18) 4
Contracted Price Cost Custom Action Custom Action Condition Custom Script Discount Category Discount Schedule Discount Tier Error Condition Favorite Favorite Product Favorite Share Import Column Import Format Install Processor Log Line Column Moover Data Migration Guide (last revised 4/9/18) 5
Localization Lookup Data Lookup Query Opportunity Opportunity Product Option Constraint Order Order Product Price Action Price Book Price Book Entry Price Condition Price Dimension Price Rule Price Schedule Price Tier Process Input Moover Data Migration Guide (last revised 4/9/18) 6
Process Input Condition Process Input Values Product Product Action Product Attribute Product Attribute Set Product Feature Product Option Product Rule Quote Quote Document Quote Line Quote Line Group Quote Process Quote Template Moover Data Migration Guide (last revised 4/9/18) 7
Quote Term Record Job Search Filter Search Index Solution Group Subscribed Asset Subscription Summary Variable Template Content Template Section Term Condition Theme Timing Log Upgrade Source Web Quote Web Quote Line Moover Data Migration Guide (last revised 4/9/18) 8
Template Access The Moover data set templates reside in.zip files on the Prodly website. Note: The templates are also available on GitHub at https://github.com/prodly/salesforce-cpq-templates. To access the data set templates from the Prodly website, perform the following steps: 1. In a web browser, navigate to the resources page of the Prodly website. 2. In the Moover Data Set Templates section, click the link for the template version you desire and download the.zip file to your computer. 3. Extract the data set template JSON files into a directory of your choosing. 4. In the Moover app, click the Moover Admin tab. The Moover Admin page appears. 5. Click Upload. A standard file browse dialog box appears. 6. Navigate to the extracted JSON files and select a file to upload. Moover imports the data set from the template file, opens the data set editor in a new browser tab, and displays the data set element for the root deployment object in the data set. Note: A warning message appears if deployment objects in the imported data set do not exist in the data model of your control organization. Refer to Schema Organization Selection for details. 7. Close the browser tab. The previous browser tab appears, displaying a message indicating successful import of the data set. Note: If you have a popup blocker enabled, Moover never opened a new browser tab. Simply refresh your browser window to continue. 8. Repeat the upload steps for each JSON file you need. Schema Organization Selection A data set uses a subset of the data model (schema) of a organization. Each data set contains a field identifying the organization that contains the schema for the data set. For obvious security reasons, the data set template files do not include the schema field values. During import, Moover defaults to using your control organization as the schema organization for the data set. Depending on your use case, the schema in your Moover control organization might not contain all the objects necessary for data deployment. The Moover data set editor allows you to use any organization you have access to as your schema organization on a per-data-set basis. If you are using an organization other than your control organization as your schema organization, perform the following steps to assign a schema organization to each data set you just imported: 1. In Moover, click the Data Sets tab. The data sets list page appears, displaying the Recently Viewed list view. Moover Data Migration Guide (last revised 4/9/18) 9
2. Click the down arrow to the right of Recently Viewed and select Data Sets (Root Elements). All your data sets, including the ones you just imported, appear in the list. Note: Prodly recommends creating a Data Sets list view identical to the Data Sets (Root Elements) list view plus a Data Set Element Name starts with SBQQ filter for easier access to the template data sets. 3. Click the link to a data set in the Data Set Element Name column. The data set editor appears. 4. C lick the Data Set Controls dropdown list (gear icon, upper right) and select Schema Settings. The Schema Settings dialog box appears. 5. In the Schema Org list, select one of the existing connections to tell the data set editor which organization contains the schema. 6. Click OK. The dialog box closes. 7. Click Save. Data Set Customization Because every implementation is unique, you need to modify the data sets to accurately reflect your implementation. This topic provides guidelines for successful use of the data set templates. Understanding and carefully choosing the unique identifier for every deployment object in each data set is essential for successful data migration. Moover allows you to combine fields to create unique composite external IDs (CEID). You can also instruct Moover to handle the IDs for you by using Moover virtual external IDs (VEID). These data set templates make some assumptions about the optimal composite external ID for each data set deployment object. Carefully review the composite external ID of each deployment object to ensure each works for your use case. For example, when a name field is part of a composite external ID, implementing the templates assumes that the names will not change over time. If a name changes in your source organization, the upsert Moover Data Migration Guide (last revised 4/9/18) 10
operation will perform an insert instead of an update, which might lead to unnecessary records and incorrect migration in the destination organization. For some objects, the record name is normally an auto number field. Because there is no way to guarantee that a destination organization will have the same auto numbering as the source organization, Moover does not allow autonumber fields to be part of a composite external ID. Thus, some objects require using almost every field in the object to create a unique composite external ID. Using long text area fields, rich text fields, and formula expression fields as part of a composite external ID might result in errors during migration. Prodly recommends not using fields with these field types in your external IDs. For example, the Price Condition and Price Action objects contain formula expression fields. Moover currently ignores such fields as part of a composite external ID. Starting with the Moover Winter 18 release, Moover will not allow such fields to be part of a composite external ID. In some cases, you might need to create a external ID field to represent a unique identifier, depending on the specific data in your source and destination organizations. Data Set Details This topic describes the default values for the data set elements and composite external IDs for each deployment object in the Moover template data sets, and also offers recommendations for which composite external IDs to carefully verify as unique identifiers for your data. Use the tables in this topic in conjunction with the data set editor in Moover to analyze the composite external ID for each deployment object. The following screenshot shows the default values for the root element in a data set. Moover Data Migration Guide (last revised 4/9/18) 11
Default Data Set Element Values The following table shows default values for the data set element attributes. For descriptions of each data set element attribute, refer to the Prodly Moover for User Guide. Data Set Element Attribute Default Value Comments Active Set Always select this checkbox. Moover only migrates data residing in active deployment objects. Replicate Owner Unset The default value is unset because the data is reference data, not transaction data. Replicate Record Type Unset does not use record types by default. Create Missing Fields Set The default value is set because implementations often involve custom fields. Sync Picklist Field Values Set The default value is set to keep the picklists synchronized. Set Audit Fields Unset Because the templates migrate reference data, not transaction data, this field is unset by default. Ignore Namespace Unset The default value is unset so Moover considers the namespace. Ignore Relationship Constraints Unset The default value is unset so Moover only moves the related records. Deployment Object Varies Refer to the next table for a list of deployment objects in the data sets. Upsert Method Standard Upsert The templates use standard upsert to prevent creating duplicate records in your destination organization and to help identify errors in your data. Query Filter None* Add query filters to migrate subsets of your data. *The following objects contain both reference and transaction data. To migrate only the reference data, the data set elements include the following query filters: Moover Data Migration Guide (last revised 4/9/18) 12
Block Price has SBQQ OrderProduct c == NULL AND SBQQ QuoteLine c == NULL Discount Schedule has SBQQ UserDefined c = false Object-Specific Settings and Composite External IDs The following table contains the following information for each deployment object: Deployment Object - Lists the names of all the deployment objects referenced in the Moover data set templates. R oot element - A checkmark in this column indicates the deployment object is a root object in exactly one data set. N on-root element - A checkmark in this column indicates the deployment object is a non-root object in at least one data set. Composite External ID Fields - Lists the fields that comprise the default composite external ID. V erify composite ID - A checkmark in this column indicates that Prodly strongly recommends very carefully double checking to verify that the corresponding composite external ID produces unique data matches for your data. These IDs in particular are known to result in duplicate data for some users. You might need to adjust these composite external IDs for your use case. $ - A checkmark in this column indicates the deployment object is multi-currency aware. The templates include the CurrencyIsoCode field in the composite external ID on multi-currency-aware objects. For multi-currency organizations, always include the CurrencyIsoCode field in your composite external IDs. For single-currency organizations, Moover ignores the CurrencyIsoCode field. Deployment Object R N Composite External ID Fields V $ Additional Document* SBQQ Product c SBQQ QuoteTemplate c SBQQ TemplateSection c SBQQ DisplayOrder c * Only SBQQ DisplayOrder c plus one other field (depending on the parent object) comprise the composite external ID. Attribute Item Attribute Set SBQQ AttributeSet c SBQQ Attribute c SBQQ Sequence c Name Moover Data Migration Guide (last revised 4/9/18) 13
Block Price Configuration Attribute Configuration Rule Cost* Name SBQQ Product c SBQQ LowerBound c SBQQ UpperBound c SBQQ PriceBook2 c CurrencyIsoCode Name SBQQ Feature c SBQQ Product c SBQQ Active c SBQQ Product c SBQQ ProductFeature c SBQQ ProductRule c SBQQ RuleEvaluationEvent c SBQQ RuleType c SBQQ Active c SBQQ Product c CurrencyIsoCode * Prodly recommends using a single Cost record per product in each currency, with the possibility of inactive duplicates. Custom Action* Name SBQQ Display_Order c SBQQ Label c SBQQ Location c * SBQQ DisplayOrder c is often different in the source and destination organizations. Custom Action Condition Name Custom Script Name Discount Category Discount Schedule Name CurrencyIsoCode Name SBQQ Type c SBQQ Product c SBQQ Pricebook c Moover Data Migration Guide (last revised 4/9/18) 14
Discount Tier Error Condition Import Column Name SBQQ Number c SBQQ Schedule c CurrencyIsoCode SBQQ FilterType c SBQQ FilterValue c SBQQ FilterVariable c SBQQ Operator c SBQQ Rule c SBQQ TestedField c SBQQ TestedObject c SBQQ TestedVariable c Name SBQQ ImportFormat c SBQQ Key c SBQQ FieldName c SBQQ ColumnIndex c Import Format SBQQ Active c SBQQ ImportFormatName c SBQQ TargetObject c Line Column Name SBQQ Section c SBQQ Template c Localization SBQQ APIName c SBQQ Language c SBQQ LineColumn c SBQQ PriceDimension c SBQQ Product c SBQQ ProductFeature c SBQQ ProductOption c SBQQ QuoteTemplate c SBQQ QuoteTerm c SBQQ TemplateContent c Lookup Data SBQQ Category c SBQQ Value c Moover Data Migration Guide (last revised 4/9/18) 15
Lookup Query Option Constraint Price Action Price Book SBQQ PriceRule2 c (was SBQQ PriceRule c in Winter 17) SBQQ LookupField c SBQQ MatchType c SBQQ Operator c SBQQ TestedField c SBQQ TestedObject c SBQQ TestedValue c Name SBQQ ConfiguredSKU c SBQQ ConstrainedOption c SBQQ ConstrainingOption c SBQQ OptionConstraintGroup c SBQQ Type c SBQQ Rule c SBQQ Order c SBQQ ValueField c SBQQ SourceLookupField c SBQQ SourceVariable c SBQQ Field c SBQQ TargetObject c SBQQ Value c Name IsActive Price Book Entry Name Pricebook2Id ProductCode CurrencyIsoCode Price Condition SBQQ Rule c SBQQ Field c SBQQ FilterType c SBQQ Value c SBQQ FilterVariable c SBQQ Object c SBQQ Operator c SBQQ TestedVariable c Moover Data Migration Guide (last revised 4/9/18) 16
Price Dimension Name SBQQ Product c SBQQ Type c SBQQ DiscountSchedule c SBQQ TermDiscountSchedule c CurrencyIsoCode Price Rule Process Input Process Input Condition Product Name SBQQ Active c SBQQ Product c Name SBQQ QuoteProcess c SBQQ Active c SBQQ MasterProcessInput c SBQQ Processinput c SBQQ Active c Name Name ProductCode IsActive Product - No Bundle Name ProductCode IsActive Product Action Product Attribute SBQQ Product c SBQQ Rule c SBQQ Type c SBQQ Attribute c SBQQ Option c SBQQ Feature c (field removed starting Spring 18) SBQQ Product c (field removed starting Spring 18) Product Attribute Set SBQQ AttributeSet c SBQQ ConfiguredSKU c SBQQ ProductOption c Moover Data Migration Guide (last revised 4/9/18) 17
SBQQ Sequence c Product Feature Product Option Product Rule Name SBQQ ConfiguredSKU c SBQQ ConfiguredSKU c SBQQ Feature c SBQQ Number c SBQQ OptionalSKU c SBQQ Active c Name SBQQ Scope c SBQQ Type c Quote Process Name Quote Template Name Quote Term SBQQ PrintOrder c SBQQ Status c SBQQ Type c SBQQ ConditionsMet c SBQQ Active c Search Filter Name Search Index* SBQQ Value c * If deploying with triggers enabled, you likely do not need to deploy this object because auto-generates it. Solution Group Name Summary Variable Name Template Content Name Template Section Term Condition Name SBQQ Template c SBQQ Operator c SBQQ TestedField c SBQQ Value c Theme Name Moover Data Migration Guide (last revised 4/9/18) 18
Upgrade Source SBQQ SourceProduct c SBQQ UpgradeProduct c Template File Contents The following table lists the JSON-formatted Moover data set template files and the data set elements contained in each. Bold text in the Data Set Elements column indicates the root deployment object of the data set in each template file. Template File Data Set Elements (bold indicates the root element) SBQQ Custom Action Data Set Template.json SBQQ Custom Script Data Set Template.json SBQQ Discount Category Data Set Template.json SBQQ Import Format Data Set Template.json SBQQ Localization Data Set Template.json SBQQ Lookup Data Data Set Template.json SBQQ Price Book Data Set Template.json SBQQ Price Rule Data Set Template.json Custom Action Condition Custom Action Search Filter Custom Script Discount Category Import Column Import Format Line Column Localization Price Dimension Product Product Feature Product Option Quote Template Quote Term Search Index Template Content Lookup Data Price Book Price Book Entry Product Lookup Query Price Action Price Condition Price Rule Summary Variable Moover Data Migration Guide (last revised 4/9/18) 19
SBQQ Product - No Bundle Data Set Template.json SBQQ Product Data Set Template.json Block Price Cost Discount Category Discount Schedule Discount Tier Lookup Query Price Action Price Condition Price Dimension Price Rule Product - No Bundle Summary Variable Upgrade Source Additional Document Attribute Item (Winter 18 only) Attribute Set (Winter 18 only) Block Price Configuration Attribute Configuration Rule Cost Discount Category Discount Schedule Discount Tier Error Condition Lookup Query Option Constraint Price Action Price Book Price Condition Price Dimension Price Rule Product Action Product Attribute (Summer 17 only) Product Attribute Set (Winter 18 only) Product Product Feature Product Option Product Rule Upgrade Source Summary Variable Moover Data Migration Guide (last revised 4/9/18) 20
SBQQ Product Rule Data Set Template.json SBQQ Quote Process Data Set Template.json SBQQ Quote Template Data Set Template.json SBQQ Quote Term Data Set Template.json SBQQ Solution Group Data Set Template.json SBQQ Theme Data Set Template.json Configuration Rule Error Condition Product Action Product Product Feature Product Rule Summary Variable Process Input Condition Process Input Quote Process Additional Document Line Column Quote Template Template Content Template Section Quote Term Summary Variable Template Content Term Condition Solution Group Theme Moover Data Migration Guide (last revised 4/9/18) 21