Search for answers or browse articles about Sintel Apps
Upgrading from Sintel Forms to Sintel Apps – Migration Guide
This article explains how to upgrade an existing Sintel Forms configuration to Sintel Apps.
The upgrade process imports your existing form configuration into the new designer and rebuilds the form structure on the same SharePoint list.
Importantly, nothing goes live until you save the form in the new designer.
Before You Start
Before beginning the migration, ensure that:
-
You have Full Control permissions on the SharePoint site.
-
There are no critical workflows currently running.
-
If your form is complex (for example it contains extensive custom JavaScript or advanced workflows) you consider testing the migration on a separate site first.
Finding Existing Sintel Forms
If you are unsure how many Sintel Forms exist on your tenant or where they are located, you can quickly view them using the Sintel Forms (classic designer).
1. Pre-Upgrade Requirements
The following steps must be completed for each form template before April 2nd 2026.
– Run Threshold Management (Required)
This step restructures the conversations list and related lists into the required folder format.
Sintel Apps only supports upgrades from forms where the conversations and linked lists store data using the following structure:
To run this:
Sintel Forms Designer → Settings → Threshold Management → Start
This will automatically reorganise the list structure.
– Add Unused Fields to the Layout (Recommended)
To prevent issues during migration, it is recommended that all unused fields are temporarily added to the form layout.
You can then place them inside a hidden section.
Steps:
- Open the Sintel Forms Designer
- Go to Layout
- In Existing Fields, click Auto-Layout
This will create a new section containing all unused fields.
You can then hide this section.

2. Install the New Version of Sintel Apps
Add the Sintel Apps application to your SharePoint tenant and deploy it.
Once installed:
- Create the Apps page on your SharePoint site.
- Open the page.
- Launch Sintel Apps from Site Contents.
Configure Sintel Apps on a Site – Sintel Apps
3. Run the Pre-Upgrade Check

Select the SharePoint list containing your form.
The upgrade wizard will run a pre-upgrade check which reviews the entire form configuration and generates a report.
The report may contain:
-Information Messages
These simply confirm that checks were performed successfully and can be ignored.
-Warnings and Errors

These must be reviewed and resolved before proceeding.
Once issues are resolved:
- Close the report.
- Refresh the page to run the check again.
- Verify that all issues are resolved.
When everything is confirmed, click Save to proceed with the upgrade.
4. Import the Existing Configuration
When you open the new version of Sintel Apps:
-
The system automatically detects existing Sintel Forms configurations on the site.
-
You will be prompted to import the configuration.
Select Yes to begin the import.
The system will then:
-
Read the existing configuration
-
Rebuild the form layout
-
Recreate logic rules
-
Recreate workflow configuration
-
Apply settings
At this stage the form is rebuilt in the new designer as a preview only.
Nothing becomes live until you click Save.
5. Review Upgrade Notifications
After the import completes, a notification pop-up will appear.
This may include:
-
Deprecated settings
-
Features requiring review
-
Minor compatibility notes
These notifications are informational alerts to help verify the upgrade.
Within the migration summary:
| Colour | Meaning |
|---|---|
| Blue | Successfully upgraded |
| Orange | Requires review |
| Red | Requires attention |
6. Typical Upgrade Issues
– Unsupported Features
Example: Migrating Conversations email notification settings is not supported.
Resolution: No action is required. Customising the email body for the Conversations feature is not currently supported.
– Rules Replaced with Custom JavaScript
Example message:
Section expand / collapse converted to JS placeholder
Resolution:
Rules containing unsupported steps will be converted into JavaScript placeholders.
These rules will be marked with the prefix:
You must review the JavaScript to ensure it works correctly in Sintel Apps.
Refer to the following articles:
– Missing Fields in Lookup Default View
Example message:
Resolution:
If your form uses lookup fields that retrieve additional columns, those fields must be visible in the default view of the lookup list.
Add the missing columns to the default view and re-run the upgrade check.
7. Important: How Saving Works
It is essential to understand how publishing works during the upgrade process.
The imported form is initially a preview only.
It does not affect live users until you click Save.
The most recently saved designer (old or new) is the active version on the SharePoint list.
8. Recommended Transition Approach
If you are not ready to immediately switch to the new version, we recommend the following process:
- Allow the form to be rebuilt in the new designer.
- Carefully review the upgraded form.
- Make any required changes or improvements.
- Click Save in the new designer to store your progress.
- Open the old Sintel Forms designer and click Save there.
Saving in the old designer after saving in the new one makes the old version the active version.
This means:
-
Your progress in the new designer is retained.
-
Live users continue using the existing stable form.
-
You can continue refining the new version.
When you are fully satisfied, simply save in the new designer to make it live.
You can move between designers during the transition period — the most recently saved version always runs on the list.
This allows upgrade and testing without disrupting users.
9. Post-Upgrade Steps
– Workflow History for Older Forms
Forms created before October 2021 may still store historical workflow data in a legacy list:
Although this list is no longer used, you may want to preserve its data.
Resolution
A Power Automate flow is available to copy historical workflow records into the main form list.
To use it:
- Download the provided solution.
- Import it into your Power Automate environment.
- Configure the three environment variables.
- Run the flow against the form list.
See:
Migrating Workflow History Using Microsoft Power Automate
– Signature Storage
Form signatures are stored in the hidden SharePoint library:
Structure:
→ LISTGUID
→ SignatureUniqueGuid.png
No migration action is required for signatures.
Summary
-
Migration rebuilds your existing form in the new designer.
-
A pre-upgrade check verifies configuration compatibility.
-
Nothing goes live until you click Save.
-
The last saved version (old or new) is always the active version.
-
You can safely return to the old designer until you are ready to switch.
This approach ensures a controlled and safe transition to Sintel Apps.
