Skip to main content
venkatesanr1106
Known Participant
October 3, 2026
Question

data migrating to new schema from appian cloud db

I am having request to create new custom schema and export the data from default Appian schema

 

 

 

I too see some above recommendations in the earlier discussion, based on my analysis i found below solutions like 

 

1) we can rename existing Appian table to new schema.table name which would move all the existing Appian table to new schema with out breaking its existing links

 

RENAME TABLE  appian.my_table TO target_schema.my_table;
 

2) we can then use Appian default capabilities to change the source table in the corresponding records  via GUI

Is this solution Okie to use , will it have any negative impact to look out ?, or do u have any other easy recommended way of doing this in appian ?

7 replies

stefanhelzle0001
stefanhelzle0001
Brainy
October 3, 2026

I think this should work, but suggest testing this procedure with a separate table and go for it if everything works as expected.

    venkatesanr1106Author
    Known Participant
    October 3, 2026

    Thanks Stefan . I have tested and it worked well .  I just would like to get others opinion how they are handling such request  in their projects  . Any other way of doing records update faster compare to manually repointing records to new schema table one by one  . 

    stefanhelzle0001
    stefanhelzle0001
    Brainy
    October 3, 2026

    I think this is a reasonable approach. If you provide more details on the actual problem you want to solve, we might be able to guide you.

      harshas2775
      harshas2775
      Brainy
      October 5, 2026

      While the RENAME table command seems sufficient to move tables from one schema to another, I would be vary about any underlying or dependent database structures like Triggers, View, Store Procedures and functions.

      You might need to drop underlying triggers first before rename statement execution. Also, you will need to recreate views and store procedure queries with new schema. Easiest way to do this is exporting all views and store procedure queries, update schema definitions for them and then run those in new database schema. 

      On Appian front, data store entities (if you have them), record type etc will need mappings to be updated. Additionally if you are using any plugin based smart service that might require jndi name, then update mappings in admin console data source page will be needed as well to prevent any errors. 

      Happy to help. Even happier to optimize.
        venkatesanr1106Author
        Known Participant
        October 6, 2026

        Thanks  Harshas for the Reply, I will take care of those ( Most of them not used : Triggers , Functions, View, Proc, ) as well.

        Any known Acceptable automation to update (repoint the schema table )  the Multiple record object in the GUI , as we are planning to move 100 + records in new schema, 

        arunkumara411233
        arunkumara411233
        Participating Frequently
        October 11, 2026

        Your approach may work, but I wouldn't recommend renaming tables directly without thoroughly validating dependencies, permissions, indexes, foreign keys, and other database objects. Appian recommends creating additional schemas mainly for new applications rather than migrating existing data. I'd suggest following the Appian Data Migration to New Schema guide and testing the migration in a non-production environment first.

        nareshs945
        Inspiring
        October 12, 2026

        Since you have already validated that RENAME TABLE works, I think the bigger challenge is updating the data sources for your 100+ existing Record Types. One alternative worth evaluating is creating the new schema with the required permissions and checking whether your existing database connection can access both schemas. This could avoid creating a separate connected system, although the Record Types would still need to reference the new schema.

        Since you have 100+ Record Types, it may also be worth raising an Appian Support case to confirm whether there is a supported migration approach that avoids manually updating each Record Type.

        Terms & ConditionsAccessibility statement