---
sourceDocument: Australia Build or modify applications
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/pt-BR/application-development

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Change the parent instance

# Change the parent instance {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 min. de leitura

If it becomes necessary to modify the instance hierarchy, you can change the parent
for a development instance.

## Antes de Iniciar

Role required: none.

## Por Que e Quando Desempenhar Esta Tarefa

Changing the parent initiates a complete comparison between the development instance
and the new parent instance. To optimize comparison speed and reduce the number of
collisions and local changes that need review afterwards, ensure that the new parent
instance was cloned recently from an appropriate instance (for example, the
production instance). Before you change the parent instance, ensure that the change
does not conflict with your change management process or other development
efforts.

To change the parent for a development instance:

## Procedimento

1. On the development instance, navigate to Team DevelopmentTeam Dashboard.
2. In the control panel, click Change.
3. Select the remote instance you want to use as the parent and click Select.  
   Alternatively, click the link to [define a new
   remote instance](https://servicenow-prod.fluidtopics.net/IF7N68~2FNOc2PT7lR~Iaw "For each instance, define other instances in the hierarchy as remote instances."). Then, repeat steps 1--3 and select the remote
   instance you defined.  

   The system initiates a reconcile, which compares the local instance to the
   parent, and then generates the list of local changes and calculates the
   number of changes that are ready to pull from the parent.
4. On the completion page, click Team Dashboard.
5. [Pull versions](https://servicenow-prod.fluidtopics.net/IX34r4BGUlwFv92utDex4w "Pulling retrieves versions of customized records from the parent instance and adds them on the development instance. Pulling does not retrieve any versions for changes made by system upgrades, but it retrieves all versions for changes made by users, not just the current version.") from the parent instance and [resolve any collisions](https://servicenow-prod.fluidtopics.net/QVMOibXZdppL~OFHOVqpjQ "A collision is detected when the pulled version and the current local version are modifications of a different version, indicating that someone else has modified the same record that you have modified. The team dashboard displays the number of collisions between the local and the parent instance.").
6. Review the local changes list and [queue or
   ignore changes](https://servicenow-prod.fluidtopics.net/7PeqQjzkxU08838XxR67iQ "Application developers can queue a local change for a push to ensure the changes are available to other developers."), as appropriate.