---
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


---

# Migrate from Service Creator

# Migrating to Creator Studio from Service Creator {#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

Creator Studio is replacing the older Service Creator tool, which will be retired in the Australia release.
Nota:  
For information on older versions of Service Creator, refer to the previous release documentation.

## Why you should use Creator Studio instead of Service Creator {#creator-studio-migrating-service-creator__section_dpm_zvw_lgc}

Creator Studio has a more modern interface than Service Creator. Creator Studio uses Record Producers directly, implements workflows with Playbooks, and allows fulfillment via Workspaces. It also integrates with deployment pipelines to promote applications created with Creator Studio to production environments.

## How to try Creator Studio {#creator-studio-migrating-service-creator__section_svz_fpw_xcc}

If you're currently using Service Creator and want to try Creator Studio, follow these steps:

* Confirm that your instance is running at least Xanadu patch 3.
* Purchase an App Engine Enterprise license.
* Download Creator Studio from the ServiceNow Store. For more information, see [Installing Creator Studio from the ServiceNow Store](https://servicenow-prod.fluidtopics.net/xw0LVx93pSSr2AqK684mLg "Installing Creator Studio from the ServiceNow Store makes it available for people to build apps on your instance.").
* Activate Creator Studio.
{#creator-studio-migrating-service-creator__ul_slg_54w_xcc}

## Playbooks vs. workflows {#creator-studio-migrating-service-creator__section_l12_hpw_xcc}

Creator Studio uses playbooks instead of workflows to automate processes in the apps you build.

[Playbooks](https://servicenow-prod.fluidtopics.net/ACNUyxL3haCoieGCkodBsQ#gloss-playbook-creator-studio "A set of automated activities that occur based on a trigger. For example, sending an email when a request is approved. Think of playbooks as pre-programmed workflows that kick in after a form is submitted. They are like if/then statements: If this happens, then that will happen.") are a series of steps triggered by an event. You can add multiple playbooks to an app if needed

The steps in a Creator Studio playbook, which include activities and decisions replace the way Service Creator used to define service configurations.

In Service Creator, you had to first create a service category, then define the service and its table. In Creator Studio, the table is automatically created when you make an app, simplifying the category selection process.

For more details, check out [Working with automation in Creator Studio](https://servicenow-prod.fluidtopics.net/k1ZhzGExg2x1TgWkDZ12QQ "How do you simplify and streamline tasks for fulfillers? Use automation! For example, you can have a task assigned automatically to someone based on what type of request it is. We’ll use playbooks to accomplish adding this automation to your app.").