Port Readiness Guide

Last updated: July 29, 2025

Moving to Clazar from Your Current Marketplace Vendor

Welcome! If you're transitioning your Marketplace presence from a previous vendor to Clazar, this guide outlines everything needed to make the switch seamless and secure across AWS, GCP, and Azure.

It includes:

  • Who should join the porting call

  • Permissions required for each cloud marketplace

  • What Clazar will handle during the call

  • Resources for security reviews and setup documentation

This guide is designed to be shared with your technical or administrative stakeholders.

We strongly recommend not setting up Clazar's cloud integrations on your own. Several key values are captured during the porting call and need to be registered in our backend to ensure your listings, buyer history, and usage data port over correctly. Performing setup outside the guided call may result in delays or data sync issues.

👥 Who Should Join the Porting Call?

Role - Why They’re Needed

Cloud Admin / Engineer

To validate permissions, deploy resources, and answer environment-specific questions

Partnership / Marketplace Ops Lead

To align on listing and Seller account Information

Security or Compliance Reviewer (optional)

If approvals are required to grant access or deploy Clazar stacks

🛠 What Will Happen on the Porting Call?

During the call, Clazar will:

  1. Walk through your current Marketplace setup (AWS, GCP, or Azure)

  2. Guide deployment of a Clazar-provided CloudFormation or configuration setup

  3. Port over:

    • Listings (titles, descriptions, pricing)

    • Buyers and entitlements

    • Contracts and private offers

    • Metering usage and historical analytics

  4. Validate everything is visible in the Clazar console

  5. Assist with testing and launch steps

✅ Permissions & Access Required

Cloud Access Needed & How to Check

AWS

Admin user with access to IAM, S3, CloudFormation

  • AWS Console → Top-right dropdown should show “Admin”

  • IAM Console

  • S3 Console

  • AMMP

  • Stack creation access: Login to Clazar > Integrations > AWS Marketplace > Clazar Role and Access > Launch Stack. Once you click launch stack, you'll be redirected AWS Portal, and if the portal does not show any Permission Error, we are good to go. You need not create the stack (we will do that over our call)

GCP

Project Owner for Marketplace project

GCP Console → Ensure Owner role

Azure

Azure Global Admin + CRM Admin (for Partner Center)

Microsoft Partner Center

AWS Co-Sell

Alliance Lead, AWS Admin

  • Alliance Lead can be verified by logging to Partner Central > Click on My Company from the top right > Verify the alliance lead name

  • AWS Admin (Stack creation access): Login to Clazar > Integrations > AWS Co-sell > Create Required Resources > Production > Create Resources.
    Now, you'll be redirected to AWS Portal, and if the portal does not show any Permission Error, we are good to go. You need not create the stack (we will do that over our call)

🧩 Cloud-Specific Data Ported

Cloud - What We Port

AWS

Listings, buyers, entitlements, metering data, private offers, analytics

GCP

Listings, subscribers, usage records, pricing history, offers

Azure

Listings, current/past buyers, contracts, metered usage, private offers, revenue/disbursement data

Please note once the cloud setup is done it will take 48 hours for the data to show up in Clazar.

🔐 For Security or Compliance Review

If your security team needs to review what’s being deployed or accessed, here’s everything you can share:

AWS Marketplace Access

AWS Co-Sell Roles Access

📚 Setup & Porting Docs by Cloud

CloudSetup Guide1-Click Port Guide

AWS

Cloud Setup

1-Click Port

GCP

Cloud Setup

1-Click Port

Azure

Cloud Setup

1- Click Port

🤝 Need Help or Have a Security Review?

We’re happy to assist! If your team needs help with deployment, security approvals, or access validation, reach out to your Clazar contact or email support@clazar.io.