Prodly Moover User Guide

Prodly Moover for Salesforce

User Guide

Winter ‘18 Release

© Copyright 2018 Prodly, Inc. All rights reserved. Prodly and Moover are trademarks of Prodly, Inc., as are other names and
marks. Salesforce and other names are trademarks of salesforce.com, inc., and are used here with permission. Other marks and
names appearing herein may be trademarks of their respective owners.

Prodly Moover for Salesforce User Guide 2

Table of Contents

CHAPTER 1 Getting Started 6
Introduction 6
Terminology 7
Installation and Configuration 8
Installation Steps 8
Configuration Steps for New Installations 10
Configuration Steps for Upgrade Installations 13
Getting Started Tutorial 19
Typical Moover Workflow 19
Organization Connections 20
Data Set Creation 22
Deployment 24
CHAPTER 2 Organization Connections 26

Overview 26
Connections Tab 26
Connections List Page 26
New Connection Creation Page 27
Connections Details Page 28
CHAPTER 3 Data Sets 31

Overview 31
Data Sets Tab 32
Data Sets List Page 32
Data Set Editor 33
Data Set Editor Header 33
Tabs View 34
List View 41
Diagram View 42
Expanded Upsert Capabilities 43
Moover Virtual External IDs (VEIDs) 43
Moover Composite External IDs 45


Additional Upsert Methods 45

Data Migration Concepts 45
Relationship Direction 45
Ignore Relationship Constraint 46
Enforce Strict Query Filter 46
Copy Relationship Value 46
CHAPTER 4 Folders 48

Overview 48
Folders Tab 49
Folders List Page 50
New Folder Creation Dialog Box 50
Folders Details Page 51
CHAPTER 5 Data Set Templates 54

Overview 54
Data Set Templates Tab 54
Data Set Templates List Page 54
Data Set Template Details Page 55
Data Set Template Entry Details Page 57
Moover Admin Tab 58
CHAPTER 6 Deployment 59

Overview 59
Deployment Center Tab 60
Deployment Results Tab 61
Deployment Results List Page 61
Deployment Result Details Page 62
Deployment Batch Result Details Page 65
Deployment Data Set Result Details Page 67
Deployment Record Result Details Page 69
Custom Report Types and Reports 70
Custom Report Types 70
Sample Report 71
CHAPTER 7 Troubleshooting 72

Support Webpages 72
Solutions Database 72
Custom Settings 72
Public Settings 72
Protected Settings 73


Further Assistance 73
APPENDIX A Lightning Components 74

DeployDataSet 75
ImportDataSet 75
APPENDIX B Field Property Details 76

Supported Salesforce Data Types 76
Scrambled Value Ranges 77
APPENDIX C Standard Picklist Support 79


CHAPTER 1 Getting Started

This chapter is a getting started guide to quickly get you up and running with Prodly Moover™ for
Salesforce with minimal time and effort. The chapter covers the following topics:
● Introduction
● Terminology
● Installation and Configuration
● Getting Started Tutorial

For more detailed explanations, refer to subsequent chapters.
Introduction
Prodly Moover is a Lightning-ready application for Salesforce® that enables rapid migration of relational
data between any Salesforce organizations. Without Moover, migrating data between Salesforce
organizations is a painstakingly slow, cumbersome process.

Moover enables migration of data in conceptually the same way Salesforce change sets enable migration
of metadata. Salesforce administrators and developers commonly use change sets to deploy project
metadata to production environments. Yet in many cases, the data (such as custom objects and settings)
also contains configuration information. Moover enables you to move both the configuration information
in the data and the data records themselves.

The following list includes a few features and uses of Moover:
● Use Moover’s centrally-controlled deployment architecture to control all deployments from a
single Salesforce organization.
● Streamline implementation of AppExchange apps and custom development.
● Replace data loader exports, remapping of parent IDs, and manual imports into production with
1-click migration.
● Establish bi-directional migration of data sets between production and sandbox organizations.
● Manage lookup and master-detail relationships on complex object data models.
● Copy test data sets to multiple developer sandboxes with 1-click migration.
● Overcome the monthly refresh interval limitation of full sandboxes.
● Migrate data between two sandbox environments to stage data for user acceptance testing
(UAT).
● Scramble personal data (such as email addresses and social security numbers) in test data
deployed to a sandbox.


● Create a backup of a Moover data set in the JSON file format and store it to GitHub.

Terminology
The following list consists of select terminology present in this document:
● Source data - Information in an organization’s database that Moover copies to another
organization during deployment.
● Schema - A set of related objects in an organization. The complete structure of the database. Just
the structure, not the data in the structure. A schema defines the relationships between objects in
an organization or application.
● Data set - A reusable set of relational data migration instructions Moover uses to determine
which objects, records, and fields Moover copies during deployment. A data set identifies the
structure of the data Moover deploys, not the data in the structure. A data set might include SOQL
query record filters as well as instructions for performing tasks such as scrambling fields or
synchronizing picklist values. A data set consists of one or more data set elements. Refer to the
data sets chapter for definitions of data set element, root element, and more.
● The following definitions describe Moover’s use of your Salesforce organizations. Depending on
the use case, a single Salesforce organization can serve multiple purposes (refer to Figure 1 for a
visual representation):
○ Control organization - The organization where you install the Moover app, build your
data sets, store your data sets, execute deployments, and manage user security
parameters. The control organization is the key to Moover’s centrally-controlled
deployment architecture.
○ Source organization - An organization containing the source data to deploy.
○ Destination organization - An organization that receives the source data during
deployment.
○ Schema organization - An organization containing the schema the data set editor uses
as the basis for building data sets in the control organization. All objects in a data set
must also exist in the source and destination organization schemas.
● Prodly Moover consists of the following components:
○ Moover application - The software program you install in your Salesforce organization,
providing the user interface to Moover.
○ Moover service - The backend portion of Moover that runs on a server in the Moover
cloud and performs the data deployment.
● Connection - Each Moover connection is a bridge between the Moover service and your
Salesforce control, schema, source, and destination organizations, which give the service limited
access to your organizations. Moover uses industry standard OAuth to eliminate the possibility of
exposing your login credentials.


● Centrally-controlled deployment - Install Moover once in a central Salesforce organization and

control all deployments from there. Establish connections to all of your organizations and deploy
between them, with any organization being a source or destination based on your need at that
time. Refer to Figure 1 for a visual representation.
Installation and Configuration

This topic provides instructions for installing and configuring the Prodly Moover application in a
Salesforce organization. The Prodly Moover application resides in a managed package on the Salesforce
AppExchange.
Installation Steps
To install the application from the managed package, perform the following steps:
1. In a web browser, navigate to the Moover installation webpage to access the installer. The Prodly
Moover installation webpage appears.
2. Click one of the following installation choices to specify the organization to use as your control
organization:
a. Install Moover in a production organization - Choose for active, trial, and developer
organizations.
b. Install Moover in a sandbox - Choose for sandboxes.


3. On the Salesforce login screen that appears, log in to the organization to use as your control
organization using your Salesforce login credentials. The Install Prodly Moover or Upgrade
Prodly Moover webpage appears.
4. Select one of the following options to give users access to Prodly Moover:
a. Install for Admins Only - This option provides access to system administrators only.
b. Install for All Users - This option provides access to all users with profiles in your
organization.
c. Install for Specific Profiles... - This option allows you to selectively choose which users
have access.

5. To optionally review additional details about the app, click View Components at the bottom of the
installation screen.


6. Click Install. The Approve Third-Party Access dialog box appears.

7. Select Yes, grant access to these third-party web sites. Continue enables.
8. Click Continue. App installation begins.
9. Once installation completes, click Done. The Salesforce Setup app appears, displaying the Home
tab containing the Apps > Installed Packages list, which shows the version number of the Moover
managed package.
10. Send an email containing the organization ID of your control organization to [email protected]
to activate your subscription or trial license. You can find your organization ID at Setup >
Company Settings > Company Information > Salesforce.com Organization ID.
Configuration Steps for New Installations

To configure your Moover new or upgrade installation, perform the following steps:


1. In the Salesforce organization where you installed Moover, navigate to Setup > Users >
Permission Sets. The Permission Sets list appears.

2. Perform the following steps to apply the Prodly Moover Admin permission set to all
Moover admins that will use the Moover application:
a. Click the Prodly Moover Admin permission set.
b. Click Manage Assignments.
c. Click Add Assignments.
d. Select the checkboxes for all relevant users.

e. Click Assign. Salesforce assigns the permission set to the user profiles.
f. Click Done.
3. Perform the following steps to apply the Prodly Moover User permission set to all Moover
users that will use the Moover application:
a. Click the Prodly Moover User permission set.
b. Click Manage Assignments.
c. Click Add Assignments.
d. Select the checkboxes for all relevant users.

e. Click Assign. Salesforce assigns the permission set to the user profiles.
f. Click Done.
4. Perform the following steps to launch the Moover app::


a. In Lightning Experience, click the App Launcher icon in the upper left of your browser
(the App Launcher dialog box appears) and click the Moover app. The Moover app
launches, displaying the contents of the Moover Home tab.
b. In Salesforce Classic, click the App Launcher dropdown list in the upper right of your
browser and select Moover. The Moover app launches, displaying the contents of the
Moover Home tab.
5. Perform the following steps to establish a connection between the Moover service and your
control organization:
a. Click the Connections tab. The Connections page appears.
b. Click New. The connection creation page for your control organization appears.

c. Optionally, in the connection name box, enter a connection name. Prodly recommends
entering Control Org.
d. Click Connect. Moover creates the connection, a new browser tab opens, and the
connection details appear.


e. Notice the checkmark for Control Org, indicating that this connection connects the
Moover service to the control organization.
f. Click the Connections tab. Your control organization connection appears in the list of
connections.
6. The Moover app currently uses standard Salesforce user interface pages that contain elements
Moover does not use. Prodly intends to remove these elements in a future release. For this
release, optionally use Setup > Edit Page to remove unused user interface elements (such as the
Activity scope tab in Lightning Experience) and customize your user experience. Some elements
(such as New Case and New Opportunity in highlights panels) are not possible to remove.
Configuration Steps for Upgrade Installations

When upgrading from an older version of Moover, perform the following additional configuration steps:
1. Perform the following steps to display the correct Upsert Method picklist values and other Data
Set object defaults in the Moover app:
a. In the Salesforce organization where you installed Moover, navigate to Setup > Objects
and Fields > Object Manager. The Object Manager page appears.
b. Click Data S et. Details for the Data Set object appear.
c. Click Fields & Relationships. The Fields & Relationships page appears. Perform the
following steps:
i. Click Upsert R ecord Handling. The field definition appears.
ii. Scroll down to the Values section.
iii. If Virtual E xternal ID is not in the list, click New and add it as the first
option in the list.
iv. Select the Default checkbox for Virtual External ID.
d. Click Page Layouts. The Page Layouts page appears.
i. Click Data S et Layout. The field definitions appear.
ii. Scroll down to the Data Set Detail section.


iii.If either Schema Org or Use Local Schema do not appear in the page layout, click
and drag their field labels from the Fields l ist and drop them in the Data Set Detail
section.
e. Click Search Layouts. The S earch Layouts page appears. Perform the following steps:
i. At the right of the screen, select Edit from the dropdown arrow for the S earch
Results layout. The Search Results layout appears.
ii. If not already there, move Data Set N ame and Folder to the Selected Fields
list.
iii. Click Save.
2. Perform the following steps to display the correct fields for the Deployment Result object in
the Moover app:
a. Navigate to Objects and Fields > Object Manager. The Object Manager page appears.
b. Click Deployment R esult. Details for the Deployment Result object appear.
c. Click Page Layouts. The Page Layouts page appears.
d. Click Deployment R esult Layout. The field definition appears.
e. Scroll down to the Deployment Result Detail section.


f. If Data Record Failures does not appear in the page layout, click and drag the Data
Record Failures field label from the F ields list and drop it just below the Result field in the
Deployment Result Detail section.
3. Perform the following steps to display the correct fields for the Deployment Batch R esult
object in the Moover app:
b. Click Deployment B atch Result. Details for the D eployment B atch Result
object appear.
d. Click Deployment B atch Result L ayout. The field definition appears.
e. Scroll down to the Deployment Batch Result Detail section.
f. If any of the following fields do not appear in the page layout, click and drag their field
labels from the Fields list and drop:them into the Deployment Batch Result Detail section:
i. Data Record Failures
ii. Data Record Failures Icon
iii. Deployment Completion Date/Time
iv. Deployment Data Set Result
v. Deployment Duration (Minutes)
vi. Deployment Duration (Seconds)
vii. Deployment Start Date/Time
viii. Result Icon
4. Perform the following steps to display the correct fields for the Deployment Record Result
object in the Moover app:
b. Click Deployment R ecord Result. Details for the Deployment R ecord
Result object appear.


d. Click Deployment R ecord Result L ayout. The field definition appears.

e. Scroll down to the Deployment Record Result Detail section.
labels from the Fields list and drop:them into the Deployment Record Result Detail
section:
i. Partial Process Stage
ii. Batch Operation
5. Perform the following steps to display the correct fields for the Deployment Data S et
Result object in the Moover app:
b. Click Deployment R ecord Result. Details for the Deployment D ata Set
Result object appear.
d. Click Deployment D ata Set R
esult Layout. The field definition appears.
e. Scroll down to the Deployment Data Set Result Detail section.
labels from the Fields list and drop:them into the Deployment Data Set Result Detail
section:
i. Data Record Failures
ii. Data Record Failures Icon
iii. Deployment Completion Date/Time
iv. Deployment Duration (Minutes)
v. Deployment Duration (Seconds)
vi. Deployment Start Date/Time
vii. Result Icon
6. Perform the following steps to display the correct tabs in the Moover app.
a. Navigate to Apps > App Manager. The App Manager page appears.
b. At the right end of the line containing the Moover app name, click the down arrow and
select Edit. The Moover (Managed) page appears.


c. Adjust the Selected Tabs list to include the following tabs:
i. Home
ii. Moover Admin
iii. Folders
iv. Connections
v. Data Sets
vi. Data Set Templates
vii. Deployment Center
viii. Deployment Results
d. Click Save.
7. Perform the following steps to launch the Moover app::
a. In Lightning Experience, click the App Launcher icon in the upper left of your browser
(the App Launcher dialog box appears) and click the Moover app. The Moover app
launches, displaying the contents of the Moover Home tab.
b. In Salesforce Classic, click the App Launcher dropdown list in the upper right of your
browser and select Moover. The Moover app launches, displaying the contents of the
Moover Home tab.
8. Perform the following steps to establish a connection between the Moover service and your
control organization:
a. Click the Connections tab. The Connections page appears.
b. Click the down arrow to the right of Recently Viewed and select All.
c. If connections from a previous Moover version appear in the list, perform the following
steps:
i. Click each connection to display the connection details and locate the
connection that has the Control Org field set. The organization with C
ontrol Org
set is your control organization.
ii. Proceed to the next numbered step.


d. If no connections appear in the list, click New. The connection creation page for your
control organization appears.

e. Optionally, in the connection name box, enter a connection name. Prodly recommends
entering Control Org.
f. Click Connect. Moover creates the connection, a new browser tab opens, and the
connection details appear.


g. Notice the checkmark for Control Org, indicating that this connection connects the
Moover service to the control organization.
h. Click the Connections tab. Your control organization connection appears in the list of
connections.
9. Perform the following steps to ensure the predefined data sets (root-level data set elements) list
view is correctly named:
a. Click the Data Sets tab. The D ata Sets page appears, displaying the Recently Viewed list
view.
b. Click the down arrow to the right of Recently Viewed and look for Data Sets (Root
Elements).
c. If Data Sets (Root Elements) is not in the list, select either Root Data Sets or Root
Elements.
d. At the right of the screen, click the List View Controls icon and select Rename.
e. Enter Data Sets (Root Elements) and click Save.
10. Perform the following steps to add the Folder Name column to the Data Sets (Root Elements) list
view:
a. At the right of the screen, click the List View Controls icon and select Select Fields to
Display. The Select Fields to Display dialog box appears.
b. Move Folder Name from the Available Fields list to the Visible Fields list.
c. Click the up and down arrows to position Folder Name t hird in the list.
d. Click Save.
11. The Moover app currently uses standard Salesforce user interface pages that contain elements
Moover does not use. Prodly intends to remove these elements in a future release. For this
release, optionally use Setup > Edit Page to remove unused user interface elements (such as the
Activity scope tab in Lightning Experience) and customize your user experience. Some elements
(such as New Case and New Opportunity in highlights panels) are not possible to remove.

Installation and configuration are now complete.
Getting Started Tutorial

This topic is a tutorial that leads you through a typical Moover workflow to copy data records from one
Salesforce organization to one or more other Salesforce organizations. This tutorial requires and
assumes that you have completed all the installation and configuration steps.
Typical Moover Workflow

The following list describes a typical Moover workflow:
1. Configure connections between the Moover service and your data source and data destination
organizations.
2. Create a reusable data set.
3. Add data set elements, containing parent and child objects and fields.
4. Deploy the data set to copy all of your related CRM data from source to destination.
5. Monitor the deployment progress.


6. Verify the deployment results.

The following sections describe the workflow steps:
● Organization Connections
● Data Set Creation
● Deployment
Organization Connections
This getting started topic lists the minimum steps you need to connect your organizations to the Moover
service. Refer to the organization connections chapter for a full description of all organization connection
features.

For the Moover service to deploy data between organizations, you must establish connections between
the Moover service and the organizations responsible for control, schema, data set, data source, and data
destination. During Moover installation and configuration, you established the connection to your control
organization (the organization that houses the Moover app, stores your data sets, and controls
deployment). This topic describes how to establish additional connections. Depending on the use case, an
organization can serve multiple purposes. In the most simple use case, the schema and source data
reside in the control organization.

The following figure of Moover’s centrally-controlled deployment architecture conceptually depicts the
install, control, schema, data set, data source, and data destination organizations as separately as
possible:

Figure 1: Moover’s centrally-controlled deployment architecture


Use the Connections tab in the Moover app to establish connections between the Moover service and
your organizations. Then later, during data set creation and at deployment, define the purpose(s) each
connection serves for your particular use case.

To establish connections, perform the following actions:
1. Determine which organizations to use as schema, data source, and data destination
organizations for your use case.
Perform the following steps for each organization:

a. Click New. The connection creation page appears.

b. In the Salesforce Organization Type list, select the type of organization.
c. Optionally, in the Connection Name box, enter a connection name.
d. Click Connect. A new browser tab opens and the Salesforce login page appears.
e. Enter your Salesforce login credentials.
Click Log In. Salesforce verifies your credentials and the Allow Access? dialog box
appears.


g. Click Allow. Moover creates the connection and the connection details appear.

h. Notice no checkmark for Control Org, indicating that this connection connects the
Moover service to an organization other than the control organization.
i. Click the Connections tab. Your newly-added connection appears in the list of
connections.

Data Set Creation

This section lists the minimum steps you need to create a data set. Refer to the data sets chapter for a full
description of all data set creation features.

Data sets inform Moover which related records to copy during deployment. Create and store as many
data sets in your control organization as you desire for all your data transfer needs.

To create a new data set in your control organization, perform the following steps:
1. Click the Data Sets tab. The d
ata sets list page appears.


2. Click New. The data set editor appears.

3. In the D
ata Set Element Name box, enter a name that doubles as both the name of the data set
and the name of the root element of your data set.
Data Set
4. The Moover data set editor needs to know which schema to use when you select the
corresponding relational data for deployment. By default, Moover uses the schema from your
control organization. To select the schema from a different organization, perform the following
steps:
a. At the right of the screen, click the Data Set Controls gear icon and select Schema
Settings. The Schema Settings dialog box appears.

b. In the Schema Org list, select one of the existing connections to tell Moover which
organization contains the schema to use during data set creation.
c. Click OK. The dialog box closes.

5. In the Deployment Object list, select an object from the list of the Salesforce standard and custom
objects to use as your root element. The object, its fields, and all objects with relationships to the
object become eligible for inclusion in the data set.

6. In the Upsert Method list, select your desired upsert method. Refer to the section covering
Expanded Upsert Capabilities for more information.
7. Click the OBJECT FIELDS tab. The list of fields in your deployment object appears.
8. Select Copy All Fields.
9. Click the CHILD OBJECTS or P ARENT OBJECTS tab. The list of objects with a child or parent
relationship to your deployment object appears.
10. Select the checkboxes for the related child and parent objects you want to include in the
deployment. Moover creates a separate data set element for each checkbox you select and each
object name highlights in the list.
11. Click the highlighted links to repeat the selection process, drilling into the objects to create a
chain of data set elements.


12. Click Save. Moover stores separate data set elements for your root deployment object and each
deployment object in the data set chain.
13. Optionally, click the Show more actions for this record down arrow in the upper right and select
Create Template to create a template of the data set (including its chain of data set elements) for
future use. Moover creates a template file in JSON format and the details page for the data set
template appears. Refer to the data set templates chapter for a full description of all data set
template features.
Deployment
This section lists the minimum steps you need to deploy a data set, monitor the progress, and verify the
results. Refer to the deployment chapter for a full description of all deployment features.

Deployment is the act of copying a set of related records from a source organization to a destination
organization.

To deploy a data set, perform the following steps:
1. Click the Deployment Center tab. The Deployment Center page appears.

2. Select the organization from the Source Salesforce Organization list that contains your source
data.
3. Select up to five destination organizations from the Destination Salesforce Organization list.
4. Select the checkbox(es) for the data set(s) you want to deploy.


5. Click Deploy. A deployment results tracking page appears, displaying the progress of the
deployment in real time.

6. Click a data set in the Deployment Data Sets Results section to see the details of the deployment
or the Deployment Results tab to see a list of deployment results for all data sets Moover
deployed from this control organization.


CHAPTER 2 Organization Connections

This chapter provides a detailed description of the connections topic introduced in chapter 1.
Overview
For the Moover service to deploy data between organizations, you must establish connections between
the Moover service and the organizations responsible for deployment control and data sets, schema,
data source, and data destination.

The first connection you establish must be to your control organization.

Use New on the connections list page to initiate creation of exactly one new connection for each
organization in your use case. Depending on the use case, an organization can serve multiple purposes.
In the most simple use case, the schema and source data reside in the control organization. Refer to the
organization connections topic in the getting started chapter for basic step-by-step connection creation
instructions.
Connections Tab
This topic describes the user interface elements available on each Connections tab page.
Connections List Page

To access this page, click the Connections tab.


This page contains the following options:
● Connections list - The list of established connections between the Moover service your
organizations. Click a connection name to display the details page for the connection. The Show
more actions down arrow at the right end of each list entry contains the following options:
○ Edit - Allows you to edit all fields from a single dialog box. Only edit the Connection
Name and the Active checkbox. The remaining fields will become read-only in a future
release.
○ Delete - Permanently removes the connection.
● List views - Displays a portion of the connections list, based on the filtered view you select.
● New - Launches the new connection creation page.
● Import - Ignore. Moover does not use this standard Salesforce element.
● List customization options - The standard set of Salesforce options for customizing the
arrangement and filtering of the list, located just below New and Import.
New Connection Creation Page

To access this page, click New on the the c onnections list page.


● Connection Name - Specifies an optional, human-readable name of the connection. When blank,
Moover sets this field to the organization’s company name during connection creation.
● Folder Name - Specifies an optional folder in which to store the connection.
● Salesforce Organization Type - Lists the available Salesforce organization types.
○ Production - Specifies login.salesforce.com as the link to use for organization
authentication during connection creation.
○ Sandbox - Specifies test.salesforce.com as the link to use for organization authentication
during connection creation.
● Custom Salesforce Domain - Specifies an optional custom Salesforce My Domain URL.
● Connect - Prompts you to select and authenticate an organization, creates a Moover connection
to that organization, and displays the details page for the connection.
Connections Details Page

To access this page, click any connection name in the connections list on the connections list page.


● New Contact - Ignore. Moover does not use this standard Salesforce element.
● Edit - Allows you to all fields from a single dialog box.
● New Opportunity - Ignore. Moover does not use this standard Salesforce element.
● Show more actions for this record - Displays a list of the following actions:
○ New Case - Ignore. Moover does not use this standard Salesforce element.
○ New Lead - Ignore. Moover does not use this standard Salesforce element.
○ Delete - Permanently removes the connection.
○ Change Owner - Allows you to name a different owner for this record.
● RELATED tab - Ignore. Moover does not use this standard Salesforce element.
● DETAILS tab - The following list describes the fields in a connection record:
○ Connection Name - Specifies the human-readable name of the connection.
○ Folder Name - Specifies an optional folder that contains the connection.
○ Expires On - Specifies the date and time the current access token expires.
○ Active - Determines whether or not the connection is available for use. Only active
connections appear in the picklists during schema and deployment organization
selection.
○ Control Org - Specifies which connection connects the Moover service to your control
organization. You should never need to adjust this field. Moover automatically selects
this checkbox when you create the connection to your control organization on the
Connections tab.
○ Org Type - Lists the following available Salesforce organization types:
■ None - Ignore. Select either Production or Sandbox for your organization type.
■ Production - Specifies login.salesforce.com as the link to use for organization


■ Sandbox - Specifies test.salesforce.com as the link to use for organization

○ Access Token - Specifies the encrypted one-time access token that the Salesforce
OAuth process returns, granting Moover access to your organization using tokens.
○ Refresh Token - Specifies the encrypted ongoing refresh token that the Salesforce
OAuth process returns, which Moover uses to exchange for a new access token once the
old one expires.
○ Created By - Displays the name of the person who created the record and the timestamp
when creation took place.
○ Owner - Displays a link to the username used to create the connection.
○ User Id - Displays the user ID of the username used to create the connection.
○ Organization Id - Displays the organization ID of the organization to which the Moover
service connects.
○ Username - Displays the username used to create the connection.
○ User Email - Displays the email address associated with the username used to create the
connection.
○ User Full Name - Displays the name associated with the username used to create the
connection.
○ Last Modified By - Displays the name associated with the username that last modified
the record and the timestamp when modification took place.


CHAPTER 3 Data Sets

This chapter provides a detailed description of the data sets topic introduced in chapter 1.
Overview
A data set is a subset of your data model (schema) you create to identify Salesforce object data to copy
from a source organization to a destination organization. Because of the recursive nature of relational
objects, what you conceptually think of as a data set is actually much more complex. The following list
consists of terminology that describes the components of a data set:
● Data set element - A portion of your data model specific to a single Salesforce object. During
data set creation in the data set editor, you select a Salesforce object, fields within that object,
and relationships to child and/or parent objects. These selections define the root element of the
data set. For each relationship you select, Moover also creates a data set element for each child
or parent Salesforce object you selected. Thus, a data set contains one data set element for each
Salesforce object in the deployment. The following list comprises each data set element:
○ Object fields - The individual fields in the data set element’s Salesforce object. Moover
functionality allows for inclusion of all fields or individual fields you select.
○ Field properties - Options for adjusting destination fields during deployment.
● Root element - The special instance of a data set element you create with New on the Data Sets
tab. The Salesforce object you choose as the deployment object in the root element becomes the
starting point from which all other objects and fields to copy stems. A data set contains exactly
one root element.
● Data set relationship - A parent-child relationship between two data set elements.

The totality of the preceding list constitutes a data set, that is, the chain of data set elements and their
relationships that Moover uses during deployment.

The data set editor is the main interface through which you interact with the Moover app. Refer to the
data set creation topic in the getting started chapter for basic step-by-step data set creation instructions.

The editor allows you to select Salesforce objects, creating data set elements and relationships which
connect Salesforce objects from the schema you select during data set creation. You create data set
elements and relationships by picking objects from the CHILD OBJECTS and P ARENT OBJECTS tabs in the
data set editor’s Tabs view to create a chain of instructions telling Moover which records to migrate and
in which order. Deployment starts at the root element and traverses the chain. Refer to t he related data
migration concept for more information.


Data Sets Tab

This topic describes the user interface elements available on each Data Sets tab page.
Data Sets List Page

To access this page, click the Data Sets tab.

● Data set elements list - Displays the list of data set elements present in your control organization.
Click a data set element name to open the data set editor. The Show more actions down arrow at
the right end of each list entry contains the following options:
○ Edit - Allows you to all fields from a single dialog box.
○ Delete - Permanently removes the data set element and all other data set elements in
the data set.
PARENT OBJECTS and CHILD OBJECTS tabs f
● Select List View - Displays a portion of the data set elements list, based on the filtered view you
select. Moover installations contain the following customized views:
○ Recently Viewed - Contains Data Set Element Name, Data Set Name, and Folder for easy
access to elements within data sets.
○ Data Sets (Root Elements) - Limits the list to just the root elements for easy access to the
data sets.


Data Sets (Root Elements) list view as

your default view.
● New - Opens the data set editor for creation of a new root element and places the cursor in the
Data Set Element Name box.
● Import - Ignore. Moover does not use this standard Salesforce element. Use Upload on the
Moover Admin tab to import data sets from data set templates.
Data Set Editor

To access the data set editor, click any data set name, data set element name, or New o
n the data sets list
page.
Data Set Editor Header

The data set editor header contains the following options:
● Breadcrumb navigation - Text in the upper left showing the shortest path from the root
deployment object to the current deployment object. Click the individual breadcrumb names to
display the data set details for that object.
● Deploy - Saves all data set elements in the data set and displays a deployment page, showing
the root element of the data set to deploy.
● Save - Saves (or creates and saves) all data set elements in the data set.
● Cancel - Discards any changes to the data set and displays the data sets list page.
○ Delete - Permanently removes the data set, including all its data set elements.


○ Clone - Duplicates the data set, including all its data set elements and relationships.
○ Create Template - Creates a template file of the data set in JSON format and creates a
data set template record in your control organization.
● Data Set Controls - Provides settings that pertain to the whole data set.
○ Schema Settings - Displays a dialog box you use to specify the organization that
contains the schema the data set editor uses for data set creation. By default, Moover
uses the schema from your control organization.
● Display As - Provides the following ways to view and edit data sets and their elements:
○ Tabs view - Arranges the data set element details on tabs. All editing takes place in Tabs
view.
○ List view - Displays the data set elements using Lightning-experience cards.
○ Diagram view - Displays an entity relationship diagram (ERD) of the data set elements.
● Folders - Provides settings that pertain to use of folders and the Folders tab.
○ Folder Name - Specifies an optional folder that contains the data set.
Tabs View
This section describes the details of the data set editor Tabs view. All data set and data set element
editing takes place in Tabs view. Access all data set elements contained in the data set chain by drilling
down to child objects and up to parent objects.

The data set details appear on the following tabs:
● ELEMENT DETAILS - Allows you to configure the following data set attributes and options:
○ Data Set Element Name - Specifies the human-readable name of the data set element.
For non-root elements, the default name is <deployment object> Element. For
the root element, the default name is blank and doubles as the name of the overall data
set.
<deployment
object> Data Set
○ Data Set Description - For root elements only, an optional description of the data set for
easier reference.
○ Deployment Object - Specifies the Salesforce object to use as the basis of the data set
element. For the root element, a picklist shows all of the Salesforce objects available in
the schema that are accessible, queryable, and can either be updated or inserted. The
objects are sorted alphabetically. All objects with relationships to the deployment object
are eligible for inclusion in the data set through the PARENT OBJECTS and CHILD


OBJECTS tabs. For non-root elements, this field is read-only, determined by your
selections on those tabs.
○ Upsert Method - Specifies the upsert method to use during deployment. All upsert
methods require use of a Moover virtual external ID, Moover composite external ID, or
Salesforce external ID. Refer to the section on expanded upsert capabilities for more
information about Moover’s custom upsert capabilities. The following methods are
available:
■ None - Instructs Moover to attempt to insert every record.
■ Virtual External ID - Manages inserts and upserts by tracking IDs through the
custom, proprietary Moover virtual ID manager, eliminating the need for
standard Salesforce virtual IDs.
■ Standard Upsert - Performs a standard salesforce.com upsert. If the SOQL query
returns more than one matching record, Moover generates an error. If one
record matches, Moover updates the record. If no record matches, Moover
inserts a new record.
■ Match First Found - If the SOQL query returns more than one matching record,
Moover updates the first record. If one record matches, Moover updates the
record. If no record matches, Moover inserts a new record.
■ Skip Duplicate - If the SOQL query returns more than one matching record,
Moover skips that source record and does not insert or update any of the
matching records in the destination organization. If one record matches, Moover
updates the record. If no record matches, Moover inserts a new record.
The default upsert method at the time of installation is virtual external ID. To change the
default upsert method, navigate to Setup > Objects and Fields > Object Manager > Data
Set > Fields & Relationships > Upsert Record Handling and select a new default in the
Values table.
○ Record Selection Criteria - Displays the following optional record selection criteria:
■ Query Filter - Specifies an optional SOQL query WHERE clause of up to 950
characters that determines which source data records to copy during
deployment.
Use this field to seed test data or copy a subset of relevant data between
organizations, especially for partial sandboxes where memory limitations
prohibit copying large amounts of data. Be aware of the following rules for this
field:
■ Specify only the notation after the WHERE clause. That is, do not enter
WHERE in the field.
■ Do not include LIMIT clauses when also using Record Selection Limit.


■ Do not include relationship field queries

(Parent_Object__r.Field_Name__c). Instead, create a formula
field to pull the value into the object itself.
■ The Salesforce bulk API does not support some query filters, such as
foreign key relationships. Refer to Bulk API Limits in the Salesforce bulk
API documentation for more information.
■ Record Selection Limit - Specifies the maximum number of records to deploy.

Leave blank to deploy all records.
○ Processing Options - Displays the following optional processing options:
■ Bulk Batch Size - Specifies the maximum number of records to deploy in each
deployment batch. When blank, Moover attempts to use the maximum allowable
number of 10,000 records. The total number of records is limited by the total CSV
size of the data in the records. Adjust this field when customization of your
organization is preventing a larger batch size from executing correctly.
○ Active - When selected, the data set element is available for deployment. When
deselected on a root element, the entire data set becomes inactive. Only data sets with
active root elements appear in the deployment center. When deselected on a non-root
element, Moover skips the associated deployment object and all of its incoming and
outgoing relationships during deployment.
○ Replicate Owner - When selected, assigns ownership of the destination record to the
owner of the source record. When deselected, assigns ownership to the username used
to establish the connection to the destination organization.
○ Replicate Record Type - When selected, sets the record type of the destination record to
the record type of the source record, if available. When deselected, sets the record type
of the destination record to the default record type of the user who established the
connection to the destination organization.
○ Create Missing Fields - Appears on root elements only and affects the entire data set.
When selected, Moover searches the destination organization for source organization
custom fields and if not found, creates the fields in the destination organization. Moover
grants access to the newly-created fields to the username used to create the destination
connection. When deselected, Moover silently ignores the source fields that don't exist in
the destination organization.
○ Sync Picklist Field Values - Appears on root elements only and affects the entire data set.
When selected, Moover ensures the destination organization’s values and status for all
picklists you select for deployment match the values and status in the source
organization. Moover adds any missing values to the destination organization and


deletes any destination organization values not present in the source organization. The
picklist appendix contains a list of the picklists Moover can synchronize during data
migration.
○ Set Audit Fields - Appears on root elements only and affects the entire data set. When
selected, Moover migrates the Salesforce audit field values from the data set’s source
records to the destination records during deployment. Salesforce records provide the
following audit fields: Created By, Created Date, Last Modified By ID, and Last Modified
Date. Moover migrates these fields on record insert only; updates retain the existing
destination record information. When deselected, the Salesforce audit field values in the
destination records reflect the deployment date and time and the username used to
create the destination connection.
○ Ignore Namespace - Appears on root elements only and affects the entire data set.
When selected, Moover ignores namespace mismatches for object and fields. If the
namespaces do not match or one organization has a namespace and the other does not,
Moover still considers the fields a match. When deselected, the namespaces must match.
○ Ignore Namespace name box - When Ignore Namespace is selected, this box specifies
the namespace to ignore.
○ Ignore Relationship Constraint - For non-root elements only (because, by definition, the
root element is never constrained). When selected, Moover copies all source
organization records of this object type to the destination organization. When deselected,
Moover copies only records related to the migrating parent or child records. Moover
applies query filters in either case. Refer to t he related data migration concept for more
information.
● OBJECT FIELDS - Displays the fields of the deployment object of the currently-selected data set
element that are available for inclusion in the data set.
○ Search by field name… - Enter a search string to display only the fields whose LABEL or
API NAME contain the string.
○ Copy All Fields - When selected, Moover deploys all of the fields in the object, even fields
you might add after creating the data set. When deselected, Moover relies on individual
field checkmarks to determine which fields to deploy.
Moover does not deploy any field that meets one or more of the following criteria:
■ System field
■ Not accessible
■ Calculated field
■ Auto number field
■ Deprecated and hidden field
■ Binary field
○ Fields list - Lists all the fields in the deployment object.
■ Checkbox - Specifies which fields to deploy when you deselect Copy All Fields.
■ LABEL - Lists the field name.
■ API NAME - Lists the name to use from the API.


■ NAMESPACE - Lists the namespace prefix for custom fields.

■ TYPE - Lists the data type of the field.
■ PROPERTIES - A subset of the following options is available on each field for
adjusting destination field values during deployment. Additional details are
available in the field properties appendix
● External ID - When selected, Moover uses the field as the external ID for
upserts. Refer to the section on Moover’s expanded upsert capabilities
for more information.
● Create Missing Fields - Appears on custom fields only. When selected,
Moover searches the destination organization for the field and if not
found, creates the field in the destination organization. When deselected,
Moover silently ignores the field.
● Sync Picklist Values - Appears on picklist fields when Sync Picklist
Values is deselected on the root element. When selected, Moover
ensures the destination organization’s values for the picklist match the
values in the source organization. Moover adds any missing values to
the destination organization and deletes any destination organization
values not present in the source organization. This checkbox appears
only for picklist fields. The picklist appendix contains a list of the picklists
Moover can synchronize during data migration.
● Set Empty - When selected, Moover sets the field to an empty value in
the destination organization.
● Scramble Value - When selected, Moover scrambles field values in the
destination organization to obfuscate sensitive information or prevent
unintended emails going to customers. Each scrambled value is a
legitimate value for its field type, to continue to pass typical validation
rules. Refer to scrambled value ranges for details.
● Fixed Value - When selected, Moover sets the field to a fixed value in the
destination organization.
○ Fixed Value Input - When Fixed Value is selected, specifies the
value to store in the destination field. You must enter date and
time values in the following formats:
■ For date: yyyy-MM-dd (for example 2018-05-10)
■ For date/time: yyyy-MM-ddTHH:mm:ss.SSSZ (for
example 2018-05-10T02:59:00.000+0000)
■ For time: HH:mm:ss.SSSZ (for example
02:59:00.000+0000)
● Delay on Insert - When selected, Moover inserts the record using the
temporary value you specify in Temporary Insert Value f or this field
during deployment, then immediately updates the record with the actual
field value. Use this feature to for certain Salesforce constraints. For
example, Salesforce does not allow migrating active contracts.


Temporarily migrating the record as a draft contract, then changing the

contract to active allows for migration.
● Deploy Last - When selected, Moover migrates the record using the
temporary value you specify in Temporary Insert Value f or this field
during deployment, then defers migration of the actual data in this field
until the end of the deployment.
○ Temporary Insert Value - When Delay on Insert or Deploy Last is
selected, specifies the temporary value to use during record
insert. You must enter date and time values in the following
formats:
■ For date: yyyy-MM-dd (for example 2018-05-10)
■ For date/time: yyyy-MM-ddTHH:mm:ss.SSSZ (for
example 2018-05-10T02:59:00.000+0000)
■ For time: HH:mm:ss.SSSZ (for example
02:59:00.000+0000)
● Copy Relationship Value - When selected, Moover copies the parent
lookup field value as is, rather than performing an upsert. Users must
guarantee the integrity of the ID manually.
■ Properties indicators - Small icons appear next to the PROPERTIES gear icon
indicating the properties you have selected. Hover over the indicators to reveal
the names of the selected properties.
● PARENT OBJECTS - Displays the Salesforce objects available for inclusion in the data set that are
parents of the deployment object of the currently-selected data set element.
○ Parent object list - Lists the LABEL, API NAME, PARENT OBJECT LABEL, PARENT OBJECT
API NAME, and PROPERTIES of each available parent object. The list does not contain
objects that meet any of the following criteria:
■ Not accessible
■ Not creatable and not updateable
■ Not queryable
■ Deprecated and hidden
The list contains the following fields:
■ Checkbox - Controls creation/deletion of data set elements farther along the
data set element chain and defines the relationship direction of the data
migration. During deployment, Moover migrates associated records only in the
direction toward the checked objects.
■ LABEL - Lists the object name. When blue, the label links to the data set element
associated with the object. Use these links to traverse the data set element chain.
■ API NAME - Lists the object name to use from the API.
■ PARENT OBJECT LABEL - Lists the parent object name.
■ PARENT OBJECT API NAME - Lists the parent object name to use from the API.
■ PROPERTIES - A subset of the following options is available on each field for
adjusting destination field values during deployment:


● Enforce Strict Query Filter - When deselected, Moover migrates records

that are required because of related lookups even when the records
don't meet your query filter criteria. When selected, Moover migrates
only the records that meet your query filter criteria. Refer to the related
data migration concept for more information.

Select/deselect the checkboxes to create/delete data set elements for the corresponding
objects and add links to the object names.

Click the object name links to traverse the relationship path to access additional objects
and fields. Navigate the path on the PARENT OBJECTS and CHILD OBJECTS tabs to
determine each element’s position in a data set chain.

● CHILD OBJECTS - Displays the Salesforce objects available for inclusion in the data set that are
children of the deployment object of the currently-selected data set element.
○ Search by label, API name, or relationship name… - Enter a search string to display only
the objects whose LABEL, API NAME, or RELATIONSHIP NAME contain the string.
○ Show Managed Only - Limits the list to objects that are part of a managed package.
○ Namespace input box - When Show Managed Only is selected, specifies the namespace
Moover uses to filter the list. Leave the box blank to filter on all managed packages.
○ Child object list - Lists the LABEL, API NAME, RELATIONSHIP ID FIELD, and NAMESPACE
of each available child object. The list does not contain objects that meet any of the
following criteria:
■ Not accessible
■ Not creatable and not updateable
■ Not queryable
■ Deprecated and hidden
The list contains the following fields:
■ Checkbox - Controls creation/deletion of data set elements farther along the
data set element chain and defines the relationship direction of the data
migration. During deployment, Moover migrates associated records only in the
direction toward the checked objects.
■ LABEL - Lists the object name. When blue, the label links to the data set element
associated with the object. Use these links to traverse the data set element chain.
■ API NAME - Lists the name to use from the API.
■ RELATIONSHIP ID FIELD - Lists the field
■ NAMESPACE - Lists the namespace prefix for custom fields.


Select/deselect the checkboxes to create/delete data set elements for the corresponding
objects and add links to the object names.

Click the linked object names to traverse the relationship path to access additional
objects and fields. Navigate the path on the PARENT OBJECTS and C HILD OBJECTS tabs to
determine each element’s position in a data set chain.
List View
The data set editor List view uses Lightning-experience cards to show key details about the elements and
their relationships to each other. No data set or data set element editing takes place in List view.

The following details appear on the cards:
● root - Displays a red icon to specify the root element in the data set.
● Data set element name in the card header - Specifies the name of the data set element.
● Object API name in the card header - Specifies the API name of the deployment object.
● Edit - Changes the display to Tabs view for data set and data set element editing.
● Element Details - Expands to display the following key details about the data set element:
○ DEPLOYMENT OBJECT - Specifies the name of the deployment object.
○ OBJECT API NAME - Specifies the API name of the deployment object.
○ STATUS - Specifies the deployment eligibility status of the data set element.
○ UPSERT METHOD - Specifies the upsert method Moover uses to migrate the data.


● Relationships - Expands to display the following key details about all relationships coming into
and going out of the data set element:
○ OBJECT API NAME - Specifies the API name of the object at the other end of the
relationship.
○ RELATIONSHIP ID FIELD - Specifies the name of the field that contains the relationship
ID.
○ RELATIONSHIP TYPE - Specifies whether this data set element’s deployment object is the
child or the parent in the relationship. The RELATIONSHIP ID FIELD resides in this data set
element’s deployment object (denoted by Child Relationship) or in the
deployment object at the other end of the relationship (denoted by Parent
Relationship).
Diagram View
The data set editor Diagram view displays an entity relationship diagram (ERD) of the elements in the data
set. No data set and data set element editing takes place in Diagram view.

● Access all data set elements contained in the data set chain by scrolling and zooming the screen.
● Mouseover any element box or relationship line to see details. Refer to List View for specific field
descriptions.
● Arrows indicate the direction of the data migration and point towards the checked objects in Tabs
view.
● Double-click any data set element box to change the display to Tabs view for data set and data
set element editing.


Expanded Upsert Capabilities

Moover provides powerful upsert features which take the standard Salesforce upsert functionality to a
whole new level.
Moover Virtual External IDs (VEIDs)

The Moover virtual external ID (VEID) manager allows you to configure a data set with upsert capability
without having to know or define any Salesforce external ID fields. New users have a much quicker time
to deployment, less ramp up effort, less frustration, and reduced learning curve. Experienced users can
simplify their data set model and streamline their deployment performance.

To use, simply select Virtual External ID from the Upsert Method picklist on the data set ELEMENT
DETAILS tab and perform a deployment. You don’t need to identify fields as part of a composite external
ID. Moover automatically creates the deployed record associations on initial deployment into an empty
destination organization. Then, Moover tracks any subsequent deployments of the same source record
ID between any of your organizations.

The following drawing depicts how a Moover VEID deployment works:


Figure 2. Migration Using VEID

1. In pass one, Moover inserts records from Org Dev X to an empty Org Prod Y using Virtual
External ID from the Upsert Method picklist.
2. In pass two, Moover updates the existing Org Prod Y records and inserts new data records into
Org Prod Y.
3. In pass three, Moover updates the existing Org Dev X records and inserts the new data records
into Org Dev X.


Moover Composite External IDs

Moover provides the following expanded capabilities for creating composite external IDs:
● Select any object field to be an external ID, not just fields which are explicitly identified as
external IDs in Salesforce.
● Select multiple fields to create a composite external ID. For example, you can uniquely identify an
account by combining its name and type.
● Select one or more parent lookup fields as an external ID to uniquely match a record under the
parent records instead of the entire organization. This technique is useful for records which do
not have a unique organization-wide identifier.
Additional Upsert Methods

For multiple matching records, Moover allows you to match and update the first record found or skip
those records entirely. You can also still perform a standard Salesforce upsert (that throws errors when
more than one record matches) based on an external ID that you previously defined in Salesforce or a
composite external ID you define in the OBJECT FIELDS tab.
Data Migration Concepts

This section describes key concepts to help you grasp the power and fine-grained control Moover offers.
Your understanding of these concepts is essential to successfully migrating only the specific data you
desire to migrate.
Relationship Direction
In the data set editor Tabs view, you select objects from the CHILD OBJECTS and PARENT OBJECTS tabs of
other objects to create a chain of data set elements that define the direction Moover moves through your
data during deployment. Which objects link to which other objects is totally under your control and what
you choose is vitally important for identifying which records to migrate and in which order.

For example, in the following diagram, Moover migrates the green records when you select Account as
the root element in the data set, Contact from the CHILD OBJECTS tab of the Account element, and
Case from the PARENT OBJECTS tab of the C ontact child element. Moover includes the blue circles
only when you also select Contact from the CHILD OBJECTS tab of the Case child element:


Figure 3: Relationship Direction

Understanding relationship direction allow you to not include additional extraneous children of a child's
parent. This concept also applies to extraneous parents
Ignore Relationship Constraint

Conversely to relationship direction, ignore relationship constraint allows you to migrate all records in an
object regardless of parent/child relationships. The method is similar to the concept of outer join. Control
this functionality with the Ignore Relationship Constraint option on the ELEMENT DETAILS tab in the data
set editor Tabs view.
Enforce Strict Query Filter

Moover allows you to use query filters to control which records to migrate. Moover’s intelligence also
recognizes and migrates records that are required because of related lookups even when the records
don't meet your query filter criteria. However, you can instruct Moover to override its intelligence and
migrate only the records that meet your query filter criteria. Control this functionality with the Enforce
Strict Query Filter option on the PARENT OBJECTS tab in the data set editor Tabs view.
Copy Relationship Value

This feature allows you to insert the lookup ID into the destination organization record, rather than
migrate the parent record data.. Control this functionality with the Copy Relationship Value option on the
OBJECT FIELDS tab in the data set editor Tabs view.


Copy Relationship Value only works when the parent record exists in the destination organization. Errors
occur when the parent record does not exist in the destination organization. An example of a valid use
case is a lookup to User records, because User records are generally present in both the source and
destination organizations


CHAPTER 4 Folders
This chapter provides a detailed description of folders.
Overview
Folders are Salesforce objects you use to organize your data set and connection object data. You can
nest folders for even greater organization.

Creating and populating folders is straightforward and simple. Use New on the folders list page to create
a folder. Then assign data sets to the folder from the Folders icon on the Data Sets tab,


and connections from the Folder Name box on the Connections tab new connection page,

and the Folder Name box on the Connections tab connection details page.
Folders Tab
This topic describes the user interface elements available on each Folders tab page.


Folders List Page

To access this page, click the Folders tab.

● Folders list - The list of your folders. Click a folder name to display the details page for the folder.
The Show more actions down arrow at the right end of each list entry contains the following
options:
○ Edit - Allows you to edit all fields from a single dialog box.
○ Delete - Permanently removes the folder.
○ Change Owner - Allows you to assign a new owner to the folder record.
● List views - Displays a portion of the folders list, based on the filtered view you select.
● New - Launches the new folder creation dialog box.
New Folder Creation Dialog Box

To access this page, click New on the the f olders list page.


● Folder Name - Specifies the name of the folder.
● Description - Specifies an optional description of the folder.
● Parent Folder - Specifies an optional parent folder to nest the new folder under. Click the box to
list the available folders.
● Owner - Specifies the owner of the folder record.
● Cancel - Closes the dialog box without creating the folder.
● Save & New - Creates the folder and clears the dialog box for another entry.
● Save - Creates the folder and closes the dialog box.
Folders Details Page

To access this page, click any folder name in the folders list on the folders list page.


○ Delete - Permanently removes the folder. Any data sets or connections residing in the
folder remain and are not assigned to any folder.
○ Clone - Creates a copy of the folder record. Data sets and connections that reside in the
original folder remain only in the original folder.
● DETAILS tab - The following list describes the fields in a folder record:
○ Folder Name - Specifies the name of the folder.
○ Description - Specifies an optional description of the folder.
○ Parent Folder - Specifies an optional parent folder to nest the new folder under. Click the
box to list the available folders.
○ Owner - Displays a link to the username used to create the folder.
○ Last Modified By - Displays the name associated with the username that last modified
the record and the timestamp when modification took place.


● RELATED tab - The following screenshot shows the RELATED tab:

The following list describes the Moover records related to folders:
○ Data Sets - Displays the data sets residing in the current folder.
■ Each entry contains the following fields:
● DATA SET ELEMENT NAME - Specifies the name of the root element in
the data set.
● OBJECT NAME - Specifies the API name of the deployment object.
● ACTIVE - Specifies the active status of the data set.
● UPSERT RECORD HANDLING - Specifies the upsert method Moover uses
during deployment.
■ View All - Displays all the data sets residing in this folder.
○ Connections - Displays the connections residing in the current folder.
● CONNECTION NAME - Specifies the name of the connection.
● ACTIVE - Specifies the active status of the connection.
● CONTROL ORG - Specifies whether or not this connection is the control
org connection. You should never need to adjust this field. Moover
automatically selects this checkbox when you create the connection to
your control organization.
● USERNAME - Specifies the owner of the connection record.
■ View All - Displays all the connections residing in this folder.
○ Nested Folders - Displays the child folders of the current folder.
■ New - Launches the new folder creation dialog box.
● FOLDER NAME - Specifies the name of the child folder.
■ View All - Displays all the child folders of this folder.
● ACTIVITY tab - Ignore. Moover does not use this standard Salesforce element.


CHAPTER 5 Data Set Templates

This chapter provides a detailed description of data set templates.
Overview
Data set templates are JSON-formatted files and contain the data set components Moover needs to
recreate the data set. The following list shows a few example uses of data set templates:
● Backup
● Transfer to another control organization
● Offsite storage
● Shared repository

A data set template file consists of the following components:
● A data set element for the root deployment object, containing settings for the entire data set
● Relationships between data set elements
● A data set element for each non-root deployment object in the data set

The following steps describe the export/import flow:
1. In the data set editor, use Create Template to create a data set template file.
2. On the data set template details page RELATED t ab, use Download to copy the file to your local
computer.
3. On the Moover Admin tab in any control organization, use Upload to import the downloaded file
and recreate the data set in that control organization.
Data Set Templates Tab

This topic describes the user interface elements available on each Data Set Templates tab page.
Data Set Templates List Page

To access this page, click the Data Set Templates tab.


● Data set templates list - The list of data set templates present in your control organization. Click a
data set template name to display the details page for the data set template. The S
how more
actions down arrow at the right end of each list entry contains the following options:
○ Delete - Permanently removes the template record (but does not delete the template
file).
● Select List View - Displays a portion of the data set templates list, based on the filtered view you
select.
● New - Ignore. Moover does not use this standard Salesforce element.
Data Set Template Details Page

To access this page, click any data set template name in the data set template list on the data set
templates list page.


○ Delete - Permanently removes the template record (but does not delete the template
file).
○ Clone - Ignore. Moover does not use this standard Salesforce element. Use Create
Template to duplicate a data set and create a new data set template record in the control
organization.
○ Generate Data Set - Creates a data set and related data set elements from the template
file.
● RELATED tab - The following list describes the Moover records related to the data set template:
○ Data Set Template Entries - Displays Moover records that describe the data set template.
Each entry describes one data set in the template.

○ Each entry contains the following fields:
■ DATA SET TEMPLATE ENTRY ID - Displays the auto-numbered ID of the data set
template entry.
■ CONTENT DOCUMENT ID - Displays the ID of the JSON-formatted template file.


■ FILE INFO - V iew displays the contents of the JSON-formatted template file. If a
blank screen appears, check your browser popup blocker.
■ FILE DOWNLOAD - Download downloads the JSON-formatted template file to
your browser downloads folder. This feature allows you to export the template
file for data set backup or for import into other Moover control organizations.
○ Notes & Attachments - Ignore. Moover does not use this standard Salesforce element.
● DETAILS tab - The following list describes the fields in a data set template record:
○ Data Set Template ID - Displays the auto-numbered ID of the data set template.
○ Template Name - Specifies the human-readable name of the data set template.
○ Description - Optional description of the data set template for easier reference.
○ Owner - Displays a link to the username used to create the folder.
○ Last Modified By - Displays the name of the person who last modified the record and the
timestamp when modification took place.
Data Set Template Entry Details Page

To access this page, click any data set template entry name in the data set template entries list on the
data set template details page.



○ Delete - Permanently removes the record (but does not delete the JSON file).
○ Clone - Ignore. Moover does not use this standard Salesforce element. Use Create
Template to duplicate a data set and create a new data set template record in the control
organization.
○ Submit for Approval - Ignore. Moover does not use this standard Salesforce element.
● DETAILS tab - The following list describes the fields in a data set template record:
○ Data Set Template Entry ID - Displays the auto-numbered ID of the data set template
entry.
○ Data Set Template - Displays the data set template ID.
○ Content Document ID -
○ Description - Optional description of the data set template entry for easier reference.
○ File Info - View displays the contents of the JSON-formatted template file. If a blank
screen appears, check your browser popup blocker.
○ File Download - D ownload downloads the JSON-formatted template file to your browser
downloads folder. This feature allows you to export the template file for data set backup
or for import into other Moover control organizations.
Moover Admin Tab

This topic describes the user interface elements available on the Moover Admin tab.

This tab contains the following options:
● Upload - Imports data set template files you (or other users) created in the data set editor and
downloaded from the data set template details page. Moover creates a data set element for each
object in the template file and adds the data set elements to the data sets list page.


CHAPTER 6 Deployment
This chapter provides a detailed description of the deployment topic introduced in Chapter 1.
Overview
Deployment is the copying of a set of data records defined by a data set from a source organization to a
destination organization. You initiate deployment by clicking Deploy in any of the following locations:
● The data set editor - Initiates deployment of a data set from any data set element in the data set.
● The deployment center - Initiates deployment of one or more data sets in one operation. For
example, if you need to deploy accounts CRM data as well as campaigns, you can initiate
deployment of both and track the entire deployment through one result record.

An application programming interface (API) is also available from Prodly that includes the following
components:
● A global apex service class PDRI.DeploymentService with various deploy methods
● A REST web service DeploymentWebService with various load methods

A deployment result tracking record monitors the progress and captures the details of the deployment.
The Deployment Results tab contains all data set deployment results, with each result broken down by
data set element(s) and individual records. Moover updates progress automatically as the deployment
executes and proceeds through each data set.

While in progress and after deployment completes, you have access to results at the following levels:
● Entire deployment - Shows tracking information and a list of data sets Moover deployed.
● Each deployed data set - Provides a list of individual records as well as record batches for each
data set element. Large deployments have separate results records for each batch of data
records Moover deploys.
● Each deployed data set element - Provides a list of the individual records Moover deployed.
● Each individual record migrated - Provides a link to both the source record Moover copied and
the destination record Moover created or updated for each record Moover deployed. This level
allows for easy auditing.


Figure 4. Moover Deployment Results Schema

If Moover encounters errors during deployment, errors appear in the results records. A successful
migration of all records in a data set element or batch results in Moover indicating success. When one or
more records in an element or batch fail to migrate successfully, then Moover sets the final status to
indicate failure.

Refer to the deployment topic in the getting started chapter for basic step-by-step deployment
instructions.
Deployment Center Tab

This topic describes the user interface elements available on the Deployment Center tab.

To access this page, click the Deployment Center tab.


● Source Salesforce Organization - Specifies the organization to copy data from.
● Destination Salesforce Organization - Specifies the organization to copy data to. Use Ctrl+click
to select up to five destinations.
● Deployment Selection - Enter a search string to display only active data sets whose data set
name, deployment object, or namespace contain the string. Leave the box blank to display all
active data sets.
● Data sets list - Lists the data sets (root elements) available for deployment. Select up to 10 data
sets to deploy.
● Deploy - Starts the deployment and displays the details page for the deployment result to
monitor progress. Status updates appear in real time as deployment progresses.

Deployment Results Tab

This topic describes the user interface elements available on each Deployment Results tab page.
Deployment Results List Page

To access this page, click the Deployment Results tab.


● Deployment results list - The list of deployment results present in your control organization. Click
a deployment result name to display the details page for the deployment result. The Show more
actions down arrow at the right end of each list entry contains the following options:
○ Delete - Permanently removes the deployment results record and the entire deployment
results tree for the deployment result.
● Select List View - Displays a portion of the deployment results list, based on the filtered view you
select.
● New - Ignore. Moover does not use this standard Salesforce element.
Deployment Result Details Page

To access this page, click any deployment result name in the deployment results list on the deployment
results list page.


● Deployment Actions - The following action buttons appear depending on the status of the
deployment:
○ Delete - Permanently removes the tracking record and the entire deployment results
tree for the deployment result. Moover does not allow this action while deployment is in
progress.
○ Pause - Pauses a deployment that is in progress. Pause appears only while a
deployment is in progress.
○ Resume - Resumes a deployment that you paused. Resume appears only while an
in-progress deployment is paused.
○ Stop - Terminates a deployment that is in progress. Stop appears only while a
deployment is in progress.
○ Rerun - Initiates another deployment of the same data sets between the same source
and destination organizations. Rerun appears only after a deployment completes.
● Deployment Results - Displays a progress bar graphically reporting the progress of the
deployment. Icons on the right give a quick reference description of the possible Result values.
● Deployment Batch Results - Displays a list of results for the data record batches Moover
deployed.
○ DEPLOYMENT BATCH RESULT NAME - Displays a link to the deployment results.
○ DATA SET - Displays the name of the data set or data set element Moover deployed.
○ RESULT - Displays an icon indicating one of the following final states of the result:
■ Success - Indicates Moover was able to migrate the batch of records
successfully.
■ Failure - Indicates Moover did not successfully migrate all records in the batch.
○ DATA RECORD FAILURES - Displays an icon indicating one of the following states of the
data record migration:


■ In progress with no failed records

■ In progress with few failed records
■ Success - Indicates Moover was able to migrate all records successfully.
■ Failure - Indicates some or all record migrations failed.
● Deployment Data Set Results - Displays a list of results for the data sets Moover deployed.
○ DEPLOYMENT DATA SET RESULT NAME - Displays a link to the deployment results.
○ DATA SET - Displays the name of the data set or data set element Moover deployed.
○ RESULT - Displays an icon indicating one of the following final states of the result:
■ Failure - Indicates some or all record migrations failed.
○ DATA RECORD FAILURES - Displays an icon indicating one of the following states of the
data record migration:
■ In progress with no failures
■ In progress with few failures
■ Deployment record failure - Indicates some record migrations failed.
■ Deployment failure - Indicates Moover did not successfully migrate any records.
○ STATUS - Displays the current status of the deployment. The field contains one of the
following values:
■ Started
■ Finished
○ ERROR - Displays any errors that occurred during deployment.
● Deployment Result - Displays the following details for the deployment:
○ Deployment Result Name - Specifies the human-readable name of the deployment
result.
○ Data Record Failures - Indicates whether or not any failures occurred during
deployment.
○ Result - Displays an icon indicating one of the following final states of the result:
■ Deployment failure - Indicates Moover did not successfully migrate any records.
○ Status - Displays the current status of the deployment. The field contains one of the
following values:
■ Started
■ Finished
○ Error - Displays any errors that occurred during deployment.
○ Owner - Displays a link to the username used to create the connection.
○ Source Connection - Specifies the Moover connection to the data source organization.
○ Destination Connection - Displays one Moover connection for each data destination
organization you selected for deployment.
○ Created By - Displays the name of the person who created the record.
○ Created Date - Displays the date and timestamp when record creation took place.
○ Last Modified Date - Displays the date and timestamp when last modification took place.


Deployment Batch Result Details Page

To access this page, click any deployment batch result name in the deployment batch result list on the
deployment data set result details page.

● Edit - Ignore. Moover does not use this standard Salesforce element.
○ Delete - Permanently removes the record.
○ Clone - Ignore. Moover does not use this standard Salesforce element.
● RELATED tab - Consists of the following sections:
○ Deployment Record Results - Displays deployment result records for each data record in
each data set element Moover deployed. Each entry contains the following fields:
■ DEPLOYMENT RECORD RESULT NAME - Displays human-readable name of the
deployment result record.
■ SOURCE RECORD URL - Displays the URL of the source record Moover
deployed.
■ DESTINATION RECORD URL - Displays the URL of the destination record Moover
deployed.
■ ERROR - Displays any errors that occurred during deployment.
○ Notes & Attachments - Ignore. Moover does not use this standard Salesforce element.
● DETAILS tab - The following list describes the fields in a record result record:


○ Deployment Batch Result Name - Displays human-readable name of the batch result
record.
○ Deployment Data Set Result - Displays the human-readable name of the parent
deployment data set result record.
○ Data Set - Displays the name of and a link to the data set element Moover deployed.
○ Operation - Displays the call to Salesforce that Moover used to migrate the record. The
following operations are possible:
■ Update - Indicates Moover used an update query.
■ Insert - Indicates Moover used an insert query.
■ Upsert - Indicates Moover used the actual Salesforce upsert command.
○ Data Set Failures - Indicates whether or not any failures occurred during deployment.
○ Result Icon - Displays an icon Indicating whether or not deployment of the record was
successful.
○ Data Set Failures Icon - Displays an icon Indicating whether or not any failures occurred
during deployment.
○ Job ID - Displays a unique ID for the deployment of the record batch.
○ Result ID - Displays a unique ID for the deployment result of the record batch.
○ Result - Displays the status of the deployment of the record batch.
○ Deployment Start Date/Time - The date and time Moover started migrating this data.
○ Deployment Completion Date/Time - The date and time Moover finished migrating this
data.
○ Deployment Duration (Seconds) - The total number of seconds Moover used to migrate
this data.
○ Deployment Duration (Minutes) - The total number of minutes Moover used to migrate
this data.


Deployment Data Set Result Details Page

To access this page, click any deployment data set result name in the deployment data set results list on
the deployment result details page.

● RELATED tab - Consists of the following sections:
○ Deployment Batch Results - Displays deployment result records for each batch of data
records Moover migrated. For large amounts of data, several batches comprise the
results for a single data set element. Each entry describes a batch of records from a
single data set element in the data set. Each entry contains the following fields:
■ DEPLOYMENT BATCH RESULT NAME - Displays human-readable name of the
batch result record.
■ DATA SET - Displays the name of and a link to the data set element Moover
deployed.
■ OPERATION - Displays the call to Salesforce that Moover used to migrate the
record. The following operations are possible:
● Update - Indicates Moover used an update query.


● Insert - Indicates Moover used an insert query.

● Upsert - Indicates Moover used the actual Salesforce upsert command.
■ RESULT - Indicates whether or not deployment of the batch was successful.
○ Deployment Record Results - Displays deployment result records for each data record in
each data set element Moover deployed. Each entry contains the following fields:
■ DEPLOYMENT RECORD RESULT NAME - Displays human-readable name of the
deployment result record.
■ DATA SET - Displays the name of and a link to the data set element Moover
deployed.
■ SOURCE RECORD URL - Displays the URL of the source record Moover
deployed.
■ DESTINATION RECORD URL - Displays the URL of the destination record Moover
deployed.
● DETAILS tab - The following list describes the fields in a deployment data set result record:
○ Deployment Data Set Result Name - Displays the human-readable name of the
○ Deployment Result - Displays human-readable name of the parent deployment result
record.
○ Result - Displays whether the deployment succeeded or failed.
○ Data Set Failures - Indicates whether or not any failures occurred during deployment.
○ Status - Displays the current status of the deployment.
○ Result Icon - Displays an icon Indicating whether or not deployment of the record was
successful.
○ Data Set Failures Icon - Displays an icon Indicating whether or not any failures occurred
during deployment.
○ Data Set - Displays the name of and a link to the data set element Moover deployed.
○ Created By -Displays the name of the person who created the record and the timestamp
○ Deployment Start Date/Time - The date and time Moover started migrating this data.
○ Deployment Completion Date/Time - The date and time Moover finished migrating this
data.
○ Deployment Duration (Seconds) - The total number of seconds Moover used to migrate
this data.
○ Deployment Duration (Minutes) - The total number of minutes Moover used to migrate
this data.


Deployment Record Result Details Page

To access this page, click any record result name in the record results list on either the deployment data
set result details page or the deployment batch result details page.

● DETAILS tab - The following list describes the fields in a record result record:
○ Deployment Record Result Name - Displays human-readable name of the record result
record.
○ Deployment Batch Result Name - Displays human-readable name of the parent data set
element result record.
○ Deployment Data Set Result - Displays the human-readable name of the grandparent
○ Data Set - Displays the data set element deployed.
○ Partial Process Stage - Indicates the stage of deployment using one of the following
values:
■ Initial - Indicates the first pass of deployment.


■ Update - Indicates the second pass of deployment to update records that are
part of a self-referencing or circular relationship.
○ Success - A checkmark indicates Moover inserted or updated the record successfully.
○ Created - A checkmark indicates Moover inserted a new record in the destination
organization.
○ Batch Operation - Displays the call to Salesforce that Moover used to migrate the batch.
The following operations are possible:
■ Insert - Indicates Moover used an insert query.
■ Update - Indicates Moover used an update query.
■ Upsert - Indicates Moover used the actual Salesforce upsert command.
■ Delete - Indicates Moover used a delete query.
■ Hard Delete - Indicates Moover performed a permanent delete.
■ Query - Indicates Moover used a view-only query.
○ Record Instances - Displays the following source and destination record information:
■ Source Record ID - Displays the unique ID of the source record Moover
migrated.
■ Source Record URL - Displays the URL of the source record Moover migrated.
■ Destination Record ID - Displays the unique ID of the destination record Moover
migrated.
■ Destination Record URL - Displays the URL of the destination record Moover
migrated.
○ Created By -Displays the name of the person who created the record and the timestamp
Custom Report Types and Reports

The Moover managed package contains Salesforce custom report types and a sample report for
deployment results.
Custom Report Types

Deployment Results - Shows overall success or failure of the deployment.

Deployment Results with Deployment Data Set Results with Deployment Batch Results - Starts at
deployment results, gets child deployment data set results, then gets the children deployment batch
results.


Deployment Results with Deployment Data Set Results with Deployment Batch Results with Deployment
Record Results - Starts at deployment results, gets child deployment data set results, gets the children
deployment batch results, and then gets the child deployment record results.

Deployment Record Results - Starts directly on record results, includes parent batch, data set, and
deployment results.
Sample Report
Today's Deployment Record Results - Report of type Deployment Record Results that retrieves all record
results created during deployments that executed on the current day and includes result, error, record,
parent batch, and result information.


CHAPTER 7 Troubleshooting
As with any software, issues invariably arise. This chapter describes approaches related to
troubleshooting and solving those issues.
Support Webpages
In addition to this user guide, the Resources, Support, and FAQs webpages at www.prodly.co/resources,
www.prodly.co/support, and www.prodly.co/faqs contain many documents, tools, and other
information to assist you in migrating data efficiently and securely.
Solutions Database
When encountering issues, start looking for answers by searching our solutions database at
www.prodly.co/support. The database is connected to our Salesforce Cases and contains detailed
descriptions of error messages and answers to many common questions.
Custom Settings
The Moover app contains both public and protected custom settings that allow you, as well as the
Moover technical support team, to customize the behavior of the app. All settings are hierarchy-based.
Public Settings
The following Moover custom settings are available to Moover admins at Setup > Custom Code (Develop
in Salesforce Classic) > Custom Settings > Moover Settings > Manage > Edit:

● Debug Deployment Email - Specifies the email address Moover uses during deployment
debugging.
● Debug Deployment - Turns deployment debug mode on and off. When selected, instead of
calling the Moover service endpoint to initiate deployment, the Moover app emails the data set to
the Debug Deployment Email address. This mechanism allows the Moover support team to
debug customer issues by reproducing and running the scenarios through a developer debugger.
● Instance Type - Points the Moover app to various instances of the Moover service, such as
development, beta, demo, and more. For use only under the guidance of the Prodly support
team.


● No Record Results - When selected, Moover creates deployment result tracking records for each
individual source data record Moover attempts to migrate.
● Object Selector Page Size - Specifies the number of objects to display in the deployment object
picklist in the data set editor. For organizations with a large number of custom objects, set a
lower number to improve performance.
Protected Settings
The following Moover custom settings are available only to the Moover support team, through granted
login access:

● Max Destination Orgs - Specifies the maximum number of destination organizations the Moover
service can deploy to during a single deployment.
● Salesforce API Version - Specifies the version of the Salesforce API that Moover uses.
Further Assistance
If you need further assistance, contact Prodly technical support at [email protected].


APPENDIX A Lightning Components

This appendix provides information about the Lightning components available for Moover.

The following components are available:
● DeployDataSet - Deploys a data set to up to five destination organizations.
● ImportDataSet - Imports a data set from a downloaded data set template file.

In Lightning Experience, to add the components to your home page, perform the following steps:
1. Navigate to Setup > Edit Page.
2. From the Custom - Managed list of Lightning components, drag and drop a component onto the
page.
3. Click Save.


DeployDataSet
The DeployDataSet component mimics the behavior of a data set deployment page.

Refer to the section on the deployment center tab for details.
ImportDataSet
The ImportDataSet component mimics the behavior of Upload on the Moover Admin tab.

Refer to the section on the Moover admin tab for details.


APPENDIX B Field Property Details

This appendix provides additional details for the field property settings Moover uses to control and adjust
destination field values during deployment.
Supported Salesforce Data Types

The following table lists the Salesforce data types and the field properties Moover supports for each:

Data Type External Set Empty Scramble Fixed Delay on Deploy Copy
ID Value Value Insert Last Relationship
Value
Auto Number N/A N/A N/A N/A N/A N/A N/A
Checkbox Yes N/A N/A Yes Yes Yes Yes
Currency Yes Yes Yes Yes Yes Yes Yes
Date Yes Yes Yes Yes Yes Yes Yes
Date/Time Yes Yes Yes Yes Yes Yes Yes
Email Yes Yes Yes Yes Yes Yes Yes
External Yes N/A N/A N/A N/A Yes Yes
Lookup
Relationship
Formula N/A N/A N/A N/A N/A N/A N/A
Geolocation No No No No No No No
Lookup Yes N/A N/A N/A Yes Yes Yes
Relationship
Number Yes Yes Yes Yes Yes Yes Yes
Percent Yes Yes Yes Yes Yes Yes Yes
Phone Yes Yes Yes Yes Yes Yes Yes
Picklist Yes Yes N/A Yes Yes Yes Yes


Picklist Yes Yes N/A Yes Yes Yes Yes

(Multi-Select)
Roll-Up N/A N/A N/A N/A N/A N/A N/A
Summary
Text Yes Yes Yes Yes Yes Yes Yes
Text No Yes Yes Yes Yes Yes Yes
(Encrypted)
Text Area No Yes Yes Yes Yes Yes Yes
(Long)
(Rich)
Time (BETA) Yes Yes Yes Yes Yes Yes Yes
URL Yes Yes Yes Yes Yes Yes Yes
Scrambled Value Ranges

This section describes the scrambled destination value ranges for the Salesforce data types that Moover
can scramble.

The following table contains value ranges for all data types that Moover can scramble:
Data Type Range
Currency ● Moover scrambles the numeric digits with random numeric digits.
● Currency fields do not contain special characters.
Date (day) 1-28

Date (month) 1-12
Date (year) 1700-4000
Email ● Moover scrambles the numeric digits with random numeric digits and
letter characters with random letters.
● Moover does not scramble special characters.
Number ● Moover scrambles the numeric digits with random numeric digits
● Moover does not scramble decimal points.
Percent ● Moover scrambles the numeric digits with random numeric digits.


● Moover does not scramble decimal points.
Phone ● Moover scrambles the numeric digits with random numeric digits.
● Moover does not scramble special characters.
Text
Text (Encrypted)
● Moover scrambles the numeric digits with random numeric digits and
Text Area
letter characters with random letters.
Text Area (Long)
Text Area (Rich)
Time (hour) 0-23
Time (minute) 0-59
Time (second) 0-59
URL ● Moover does not scramble http, https, or special characters.
● Moover scrambles the remaining numeric digits with random numeric
digits and letter characters with random letters.


APPENDIX C Standard Picklist Support

This appendix provides details regarding Moover support for synchronizing the Salesforce standard
picklists between source and destination organizations during data migration that you identify for
migration on the data set or in the individual field properties.

Salesforce API version 38.0 and later define standard picklists with the StandardValueSet data
type. Previous Salesforce versions define standard picklists with the CustomField data type.

The following table lists the name of each Salesforce standard picklist as a standard value set, as its
corresponding field name, and whether or not Moover can synchronize the picklist during data
migration:
Standard Value Set Name Field Name Moover
(API version 38.0 and later) (API version 37.0 and earlier) Can Sync
AccountContactMultiRoles AccountContactRelation.Roles Yes
AccountContactRole AccountContactRole Yes
AccountOwnership Account.Ownership Yes
AccountRating Account.Rating Yes
Lead.Rating
AccountType Account.Type Yes
AssetStatus Asset.Status Yes
Campaign.Status Campaign.Status Yes
Campaign.Type Campaign.Type Yes
CampaignMember.Status CampaignMember.Status Yes
CaseContactRole CaseContactRole.Role Yes
CaseOrigin Case.Origin Yes
CasePriority Case.Priority Yes
CaseReason Case.Reason Yes
CaseStatus Case.Status Yes
CaseType Case.Type Yes
ContactRole OpportunityContactRole.Role Yes
ContractContactRole ContractContactRole.Role Yes


ContractStatus Contract.Status No

EntitlementType Entitlement.Type Yes
EventSubject Event.Subject No
EventType Event.Type Yes
FiscalYearPeriodName Period.PeriodLabel No
FiscalYearPeriodPrefix FiscalYearSettings.PeriodPrefix No
FiscalYearQuarterName Period.QuarterLabel No
FiscalYearQuarterPrefix FiscalYearSettings.QuarterPrefix No
IdeaCategory IdeaTheme.Categories Yes
IdeaMultiCategory Idea.Categories Yes
IdeaStatus Idea.Status Yes
IdeaThemeStatus IdeaTheme.Status No
Industry Account.Industry Yes
Lead.Industry
LeadSource Account.AccountSource Yes
Lead.LeadSource
Opportunity.Source
OpportunityCompetitor OpportunityCompetitor No
OpportunityStage OpportunityStage Yes
OpportunityType OpportunityType Yes
OrderType Order.Type Yes
PartnerRole Account.PartnerRole No
Product2Family Product2.Family Yes
QuestionOrigin Question.Origin No
QuickTextCategory QuickText.Category Yes
QuickTextChannel QuickText.Channel Yes
QuoteStatus Quote.Status Yes
RoleInTerritory2 UserTerritory2Association.RoleInTerritory2 Yes
SalesTeamRole OpportunityTeamMember.TeamMemberRole Yes
SalesTeamRole UserAccountTeamMember.TeamMemberRole No
AccountTeamMember.TeamMemberRole
UserTeamMember.TeamMemberRole


Salutation Contact.Salutation No

Lead.Salutation
ServiceContractApprovalStatus ServiceContract.ApprovalStatus Yes
SocialPostClassification SocialPost.Classification Yes
SocialPostEngagementLevel SocialPost.EngagementLevel Yes
SocialPostReviewedStatus SocialPost.ReviewedStatus Yes
SolutionStatus Solution.Status Yes
TaskPriority TaskPriority Yes
TaskStatus TaskStatus Yes
TaskSubject TaskSubject No
TaskType TaskType Yes
WorkOrderLineItemStatus WorkOrderLineItemStatus Yes
WorkOrderPriority WorkOrderPriority Yes
WorkOrderStatus WorkOrderStatus Yes


Prodly Moover User Guide

Uploaded by

Copyright:

Available Formats

Prodly Moover User Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Prodly Moover User Guide

Uploaded by

Copyright:

Available Formats

Prodly Moover for Salesforce

Winter ‘18 Release

CHAPTER 2 Organization Connections 26

CHAPTER 3 Data Sets 31

Additional Upsert Methods 45

CHAPTER 4 Folders 48

CHAPTER 5 Data Set Templates 54

CHAPTER 6 Deployment 59

CHAPTER 7 Troubleshooting 72

Further Assistance 73

APPENDIX A Lightning Components 74

APPENDIX B Field Property Details 76

APPENDIX C Standard Picklist Support 79

CHAPTER 1​ Getting Started

● Centrally-controlled deployment​ - Install Moover once in a central Salesforce organization and

Installation and Configuration

6. Click ​Install​. The ​Approve Third-Party Access​ dialog box appears.

Configuration Steps for New Installations

d. Select the checkboxes for all relevant users.

d. Select the checkboxes for all relevant users.

Configuration Steps for Upgrade Installations

d. Click ​Deployment​ R ​ ecord​ ​Result​ L ​ ayout​. The field definition appears.

Getting Started Tutorial

Typical Moover Workflow

6. Verify the deployment results.

Perform the following steps for each organization:

Data Set Creation

2. Click ​New​. The ​data set editor​ appears.

CHAPTER 2 Organization Connections

Connections List Page

New Connection Creation Page

Connections Details Page

■ Sandbox ​- Specifies test.salesforce.com as the link to use for organization

CHAPTER 3 Data Sets

Data Sets Tab

Data Sets List Page

PARENT OBJECTS​ and ​CHILD OBJECTS​ tabs f​

Data Sets (Root Elements) list view as

Data Set Editor

Data Set Editor Header

■ Do not include relationship field queries

■ Record Selection Limit​ - Specifies the maximum number of records to deploy.

■ NAMESPACE ​- Lists the namespace prefix for custom fields.

Temporarily migrating the record as a draft contract, then changing the

● Enforce Strict Query Filter​ - When deselected, Moover migrates records

Expanded Upsert Capabilities

Moover Virtual External IDs (VEIDs)

Moover Composite External IDs

Additional Upsert Methods

Data Migration Concepts

Ignore Relationship Constraint

Enforce Strict Query Filter

Copy Relationship Value

Folders List Page

New Folder Creation Dialog Box

Folders Details Page

● RELATED tab​ - The following screenshot shows the ​RELATED ​tab:

CHAPTER 5 Data Set Templates

Data Set Templates Tab

Data Set Templates List Page

CHAPTER 1 Getting Started

● Centrally-controlled deployment - Install Moover once in a central Salesforce organization and

6. Click Install. The Approve Third-Party Access dialog box appears.

d. Click Deployment R ecord Result L ayout. The field definition appears.

2. Click New. The data set editor appears.

■ Sandbox - Specifies test.salesforce.com as the link to use for organization

PARENT OBJECTS and CHILD OBJECTS tabs f

■ Record Selection Limit - Specifies the maximum number of records to deploy.

■ NAMESPACE - Lists the namespace prefix for custom fields.

● Enforce Strict Query Filter - When deselected, Moover migrates records

● RELATED tab - The following screenshot shows the RELATED tab:

● Insert - Indicates Moover used an insert query.