--- title: "[Contentstack Command-line Interface (CLI)] - Import Content Using the Seed Command" description: Import content into a Contentstack stack from GitHub repositories using the Contentstack CLI seed command. url: https://www.contentstack.com/docs/developers/cli/import-content-using-the-seed-command product: Contentstack doc_type: how-to audience: - developers version: unknown last_updated: 2026-03-25 --- # [Contentstack Command-line Interface (CLI)] - Import Content Using the Seed Command This page explains how to use the Contentstack CLI `seed` command to import content into a stack from GitHub repositories. It is intended for developers who want to migrate or bootstrap stack content quickly, and should be used when setting up a new stack or populating an existing stack from a public GitHub source. ## Import Content Using the Seed Command The `seed` command in the Contentstack CLI allows you to import content into your stack from GitHub repositories. It helps you migrate content with minimal steps and setup. You can import content into your stack from the following sources: - **Contentstack’s GitHub Organization**: We provide sample content that you can import directly into your stack using the `seed` command. Learn how to [import from Contentstack’s GitHub organization](#import-from-contentstack-s-github-organization). - **Non-Contentstack GitHub Repository**: You can also import stack content from any public GitHub repository owned by an individual or organization. Learn how to [import from a non-Contentstack GitHub repository](#import-from-a-non-contentstack-github-repository). ## Prerequisites - [Contentstack account](https://www.contentstack.com/login) - Contentstack CLI [installed](/docs/developers/cli/install-the-cli/) and [configured](/docs/developers/cli/configure-regions-in-the-cli/) - CLI [authenticated](/docs/developers/cli/cli-authentication/) - [GitHub](https://github.com/) access and working knowledge ## Commands To use the `seed` command, choose one of the following options to import content into your stack. - [Import from Contentstack’s GitHub Organization](#import-from-contentstack-s-github-organization) - [Import from a Non-Contentstack GitHub Repository](#import-from-a-non-contentstack-github-repository) **Note**: To upload your stack’s content to a GitHub repository for others to import, refer to the steps in the [Upload Stack's Content on GitHub](#upload-stack-s-content-on-github) section. ## Import from Contentstack’s GitHub Organization You can import content directly from Contentstack’s GitHub organization using the CLI. To begin, run the following command in your terminal: ``` csdx cm:stacks:seed ``` After running the command, you’ll be prompted to complete the following steps: - **Stack to import**: Select a stack from the list of available source stacks. - **Organization name**: From the list of organizations you have access to, select the one where your source stack is located or where you want to create a new stack.**Note**: You must be an [owner](/docs/owners-and-admins/organization-roles/#organization-owner) or [admin](/docs/owners-and-admins/organization-roles/#organization-admin) of the selected organization. - **Stack preference**: You’ll be prompted to choose one of the following options. **Create a new stack**: Enter a name, and the CLI will begin the stack creation process. - **Use an existing stack**: Select a destination stack from the list of stacks you have access to within the selected organization. If the selected stack contains existing content, the CLI will prompt you to confirm before continuing.**Additional resource**: Refer to the [Stack Roles](/docs/developers/invite-users-and-assign-roles/types-of-roles) documentation to learn more about permissions. **Tip:** To minimize errors, we recommend creating a new destination stack. If importing content into an existing stack, ensure that it is empty. The content will be imported into the selected destination stack. ## Import from a Non-Contentstack GitHub Repository You can import content from your GitHub repository into your stack using this option. Before doing so, ensure your GitHub repository contains the content. To upload content, follow the steps in the [Upload Stack’s Content on GitHub](#upload-stack-s-content-on-github) section. **Note**: The GitHub repository must be public. To import content, run the following `seed` command: ``` csdx cm:stacks:seed --repo “” ``` After running this command, you’ll be prompted to select an organization and a stack, as described in the [Import from Contentstack’s GitHub Organization](#import-from-contentstack-s-github-organization) section. Alternatively, you can run the command with all required parameters in a single line. **Options:** - `-r`, `--repo=repo`: GitHub organization name or GitHub user name/repository name. - `-k`, `--stack-api-key=stack-api-key`: Provide the stack API key to seed content to. - `-o`, `--org=org`: Provide the organization UID to create a new stack. - `-n`, `--stack-name=stack-name`: Provide the name of the new stack that must be created. - `-a`, `--alias=alias`: Alias of the management token. - `-s`, `--stack=stack`: Provide the stack UID to seed content. - `-y`, `--yes=yes`: [Optional] Skip the stack confirmation. **Examples**: - To import content from the "blog" repository in the "Stackcontent" organization, run: ``` csdx cm:stacks:seed --repo "Stackcontent/blog" ``` - To import content from a personal GitHub repository, replace the organization name with your GitHub username: ``` csdx cm:stacks:seed --repo "username/blog" ``` - To import content into a specific stack, run: ``` csdx cm:stacks:seed --repo "" -k "" ``` - To create a new stack in your organization and import content, use: ``` csdx cm:stacks:seed --repo "" --org "" -n "" ``` This command creates a new stack in your organization and imports the content into it. ## Upload Stack’s Content on GitHub Before uploading your stack’s content to GitHub, export it using the following steps. - Create a public repository in this format: `stack-`. For example, `stack-exportdata`, `stack-gatsby-website`, etc. - On your local machine, create a folder named “stack”. - Open your terminal and log in to the CLI: ``` csdx auth:login ``` This command prompts you to provide your Contentstack account credentials. - After successful login, export your stack’s content to the `stack` folder: ``` csdx cm:stacks:export -k -d “” ``` **Note**: If the management token is not specified, the `export` command uses **Auth token** by default. This command exports your stack’s content and saves it to the `stack` folder. - Open Git Bash and follow [GitHub’s documentation](https://docs.github.com/en/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line) to upload the `stack` folder to your repository.**Additional Resource:** Refer to this [sample repository](https://github.com/contentstack/stack-starter-app) in Contentstack's GitHub organization to learn the folder structure for uploading content. **Note: **To avoid the following error, create a GitHub release before importing content. `Error: Unable to find a release for '/'` Now any user can import your stack’s content to their stack by performing the steps mentioned in the [Import from a Non-Contentstack GitHub Repository](#import-from-a-non-contentstack-github-repository) section. ## Points to Remember - To import content into an existing destination stack, ensure you have permission to create content in that stack. - To create a new stack for storing content, you must have “[owner](/docs/owners-and-admins/organization-roles#organization-owner)” or “[admin](/docs/owners-and-admins/organization-roles#organization-admin)” rights in that organization. ## Common questions ### Does the GitHub repository need to be public? Yes. **Note**: The GitHub repository must be public. ### Can I import into an existing stack? Yes, but if the selected stack contains existing content, the CLI will prompt you to confirm before continuing, and you should ensure the stack is empty to minimize errors. ### What permissions do I need to create a new stack during seeding? You must be an [owner](/docs/owners-and-admins/organization-roles/#organization-owner) or [admin](/docs/owners-and-admins/organization-roles/#organization-admin) of the selected organization. ### How do I upload my stack’s content so others can import it? Export your stack’s content to a local `stack` folder and upload it to a public GitHub repository in the format `stack-` using GitHub’s command-line steps.