---
schema_version: "1"
id: 0932c0f7725bcbf9270a2ce26904f39d0129ccc26a0e4e6e837155f1f89beacc
title: Deploy Packaged Items
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/mktg/264-0-0/mc_overview_deploy_packaged_solution.md
canonical_url: https://help.salesforce.com/s/articleView?id=mktg.mc_overview_deploy_packaged_solution.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 1e75384187eb768b5592c8c86965638d39e1a1cbc8ae47d1768e6634046244a1
description: Marketing Cloud Engagement business units and enterprise accounts support package installations from AppExchange and ZIP.
products:
  - Marketing
  - Marketing Cloud Engagement
release: "264"
---
# Deploy Packaged Items

Marketing Cloud Engagement business units and enterprise accounts support package installations from AppExchange and ZIP.

To avoid permissions errors as you work, review the contents of the package and assign any necessary create or edit permissions for each item before you start.

1. Hover over the Platform menu and select **Package Manager**.
2. On the Deployment tab, click **Deploy** and choose a deployment method.
    
    If you’re uploading a ZIP package, drag it into the box or click **Upload** to find the file on your computer.
    
    If you’re deploying an installed package, click **Choose Solution Package** and find your package in the list.
3. You can enter folder structure names and text to prepend or append to the items. You can also add a unique timestamp to each file.
    
    Folders are placed directly under the root folder of each app. For example, NewFolder/item.
    
    If you preserved the folder structure when you created the package, the new folder still is inserted directly under the root folder. For example, NewFolder/YourStructure/YourStructure/item.
4. Enter and save values for any customizable fields.
5. Click **Next**.
6. Review the items and resolve any issues.
    
    If you rename an item, click **Refresh** to apply your changes.
    
    When updating a deployed package, use the Action menu to select how to handle updated items. You can keep the existing version, update to the new version, or keep both items by renaming the new version.
    
    You can update all supported items, except filter data extensions, synchronized data extensions, and data extensions that your business unit doesn’t have permission to update.
    
    If your package contains new items, you can create or skip them.
    
    You can skip items only if they have no required dependencies or if they’re a dependency of an item that has been skipped or reused.
7. Click **Deploy**.
8. Review the Deploy Summary, and check that everything deployed correctly.

#### See Also

- [Permissions for Setting Up Marketing Cloud Engagement](https://help.salesforce.com/s/articleView?id=mktg.mc_overview_permissions_setup.htm&release=264.0.0&type=5 "Review the permissions that enable Setup and admin functionality in Marketing Cloud Engagement.")
- [Package Items for Use in Marketing Cloud Engagement](https://help.salesforce.com/s/articleView?id=mktg.mc_overview_create_package_solution.htm&release=264.0.0&type=5 "Create a packaged solution to contain fully configured journeys, automations, content assets, data extensions, attribute groups, and more.")
- [Update Packaged Items](https://help.salesforce.com/s/articleView?id=mktg.mc_overview_edit_package_solution.htm&release=264.0.0&type=5 "To keep your Marketing Cloud Engagement packages working as expected, update them regularly.")
- [Package Manager Supported Actions](https://help.salesforce.com/s/articleView?id=mktg.mc_overview_package_manager_supported_actions.htm&release=264.0.0&type=5 "Here are some actions you can take when deploying a packaged solution with Package Manager in Marketing Cloud Engagement.")
- [Package Manager Notifications](https://help.salesforce.com/s/articleView?id=mktg.mc_overview_package_manager_notifications.htm&release=264.0.0&type=5 "If a packaged solution has unsupported objects, a notification appears before you deploy the package. To help you troubleshoot issues, review this list of in-app notifications.")