Create a Feature Migration Template

Overview

This details the step-by-step process to create a standard/community nCino migration template.

What is a Feature Migration Template?

A Feature Migration Template in AutoRABIT is essentially a blueprint that helps you manage and automate the process of moving features from one environment to another. It’s like a checklist that defines exactly what should be moved, how it should be transferred, and in what order — ensuring everything gets to the new environment correctly, without missing any critical steps.

The template saves time and effort by letting you set up migration rules once and use them repeatedly for consistent, error-free deployments. Whether you're moving configurations, customizations, or entire features, the template streamlines the whole process, making it much smoother and more predictable.

Standard vs Community Templates

Standard Feature Templates: These are templates that are pre-defined and ready to be used by customers/partners. Such templates are updated regularly as nCino releases changes to any configurations. AutoRABIT provides several default templates to be directly used by our community for migrating Record-Based Configurations (RBCs).

Community Feature Templates: Community templates are non-standard templates. In other words, users can define their own migration templates that are not already published by AutoRABIT. Community templates are useful if there are any customizations in nCino users want to migrate that are not listed as part of the default Standard templates.

Community templates, just like the Standard ones, are designed to be long-lasting. They need to be created once, and then can be used multiple times as a template.

Procedure

1. Hover your mouse over the nCino module and click on the option: Feature Management.

1. Click on New Feature Migration Template button.

1. On the next screen, click Create New to create a fresh template and include objects of your choice.

1. You'll be taken to the record-based configuration section, where you will find three tabs that need completed to proceed ahead:

   • Metadata Configuration

   • Record Configuration and

   • Preview and Save

Metadata Configuration

Metadata in the context of nCino is the same as that of Salesforce. It includes a collection of nCino customizations and configurations that together form a blueprint for your lending processes, e.g., Page Layout, Custom Field, Workflows and Automation.

Under Feature Details, enter the items below:

1. Name: Provide a feature migration template name.

2. Associated Partner: The default associate partner would be nCino, which you can change if necessary.

3. Version: Enter the version number here. If you're creating the feature template for the first time, it is recommended to keep the version number as 1.0.

Under the Salesforce Org Details section, do the following:

1. Choose your Salesforce Org.

2. Click Fetch Objects to retrieve all available objects in the selected Source Org.

3. By default, only nCino objects available in the Source Org will be auto-populated. To view all the objects available, click on Show All Objects.

4. Using/button, you can select/deselect all the objects for your template. Or, use the Ctrl key and select multiple objects of your choice and move them to the selected tab using the/button. Once you have selected the object, ARM will retrieve the fields included in that object behind the scenes.

1. Click on Next to go to the Record Configuration Tab.

Record Configuration

This section allows users to configure nCino records. The nCino platform that will be available to your end users solely depends on how the records are configured. Every record of nCino that the end user interacts with, you can configure a different outcome for the same. The entire platform’s behavior lies on these Record-Based Configurations (RBCs).

1. Selected List

   This list shows the objects that you have explicitly picked to include in your migration. These are the features or configurations you actually want to move, like specific custom objects that are part of the change you're working on.

2. Related List

   Objects in this list are automatically identified by AutoRABIT as being related to your selected objects. For example, if your selected object has lookup relationships or dependencies, those related objects will appear here. This ensures all necessary dependent data is considered during migration.

3. Required List

   These are objects that AutoRABIT identifies as essential for the integrity of the migration. They are mandatory and cannot be removed from the template. This typically includes standard Salesforce objects or configurations that are foundational to the selected features.

4. Excluded List

   This list comprises objects that are not required and have been explicitly excluded from the migration. You might place objects here to prevent unnecessary data from being migrated, especially if it's irrelevant to the current feature or could cause conflicts in the target environment. Note that such objects in the excluded list are still available for user selection (case-by-case basis).

   AutoRABIT automatically groups related objects into different buckets based on how they’re connected. While it’s not required, you’ll need to apply at least one filter to each bucket. By default, AutoRABIT marks one object in each bucket as the "entry point" — that’s the object the filter will apply to. Although you can choose any object, it’s generally a best practice to apply the filter to the entry point itself, since that helps keep things clean and consistent.

Based on the relationship between the objects, the AutoRABIT application will segregate the object sets, and applying a filter to each bucket is mandatory. By default, AutoRABIT will denote an object in a bucket as an entry point, which can be applied by a filter. This is not mandatory, but as a best practice, AutoRABIT recommends applying filters to the entry point object rather than any other object.

The entry object is selected by default, and the user can apply a filter. The entry object is denoted by “E”.

Applying the Filters

Apply the filter(s) using the steps as shown below:

Click Add.

The filter query is added and displayed in the filter box. You can edit the query if any modification is required. Nevertheless, multiple queries can be added based on your requirements. Validate your query to see whether the query entered is stable. Additionally, you'll be able to view several records that will get fetched.

You can also use the Query Editor to execute an SOQL query on the selected Source Org. Results are displayed in a Query Results grid.

Similar steps are to be followed for objects in other buckets as well.

Once done, click Next to proceed to the Preview and Save screen.

Preview and Save

This is the summary page for the Feature Migration template you're about to create. You can view the features details, and filters you have applied for the last time before the template is created. Any change log information that needs to be added can be mentioned in the Change Log box.

Click Save, and you will be redirected to the Feature Migration Summary screen, where you can track your template recently created.