Frequently Asked Questions

An Atlassian Solution Partner is a company vetted, trained, and certified by Atlassian to deliver consulting, implementation, training, and licensing services for the Atlassian product family — Jira, Jira Service Management, Confluence, Atlassian Assets, Bitbucket, and others. Solution Partners go through a formal accreditation process, maintain certified consultants, and have direct support escalation paths into Atlassian. Avaratak is an accredited Atlassian Solution Partner and Training Partner, which means your engagement is backed by Atlassian's partner ecosystem rather than an unaffiliated freelancer or general IT firm.

We are a boutique firm with deep, narrow expertise: Jira Software, Jira Service Management, Confluence, and Atlassian Assets. We don't dabble in twelve other platforms. Our typical work includes net-new implementations, Atlassian Cloud migrations, JSM rollouts for IT and non-IT teams (HR, Legal, Operations), Assets/CMDB design, custom workflows and automations, ScriptRunner solutions, governance frameworks, training delivery, and licensing. If your problem lives in the Atlassian stack, it lives in our wheelhouse.

Three differences. First, every engagement is led by senior practitioners — you do not get sold to by a partner and then handed off to a junior. Second, we publish upfront pricing and won't pad hours; we'd rather lose a deal than win one we can't deliver cleanly. Third, we are obsessively focused on the Atlassian stack, which means we know the corners, edge cases, and sharp edges that generalists tend to discover the expensive way.

Our headquarters is in Plover, Wisconsin, but we deliver client engagements remotely across the United States. Most of our work is delivered through video conferencing, collaborative whiteboarding, and direct work in your Atlassian instance. We can travel for kickoffs, executive briefings, or on-site training when the engagement justifies it.

Yes. As an authorized Atlassian Solution Partner, we can quote, sell, and renew licenses for the entire Atlassian product family — Cloud, Data Center, and Marketplace apps. Our pricing matches what you'd pay direct to Atlassian, and you get a partner relationship layered on top: renewal forecasting, true-up planning, sizing recommendations, and direct partner-channel escalation paths into Atlassian support when something needs to move faster than the normal queue.

Atlassian Cloud is Atlassian-hosted, automatically updated, and licensed per user with tiered Standard, Premium, and Enterprise plans. Data Center is self-hosted, licensed annually based on user tier, and gives you more direct control over performance, backups, and integrations. Atlassian has fully retired Server, so the practical decision today is Cloud versus Data Center. Most organizations are migrating to Cloud; Data Center remains relevant for regulated industries, large enterprises with specific data residency or compliance requirements, or environments with deep custom integration needs.

It depends on size and complexity, but a useful range: a small organization (under 100 users, low customization, no Marketplace app sprawl) can be migrated in 4 to 6 weeks. A mid-market migration (500 to 2,000 users with custom workflows, Marketplace apps, and Confluence content) typically runs 3 to 6 months. Enterprise migrations with significant customization, multiple instances to merge, or strict compliance windows can extend to 9 to 12 months. The longest pole is almost never the data move itself — it is workflow rationalization, app remediation, and user acceptance testing.

Migration services are typically priced as a fixed-fee scope-of-work or as hourly time-and-materials, depending on the level of unknowns going in. As a rough order of magnitude, our smaller engagements have started in the low five figures, and our larger enterprise migrations have been six-figure programs spread across multiple phases. The ROI conversation is more important than the sticker price: most of our migration clients see meaningful TCO reduction within 12 months because Cloud eliminates infrastructure, reduces administrative load, and delivers Atlassian's newest features without upgrade cycles.

Most popular Marketplace apps have Cloud equivalents, but not all of them, and not all features carry over one-for-one. The first concrete deliverable in any migration we run is a Marketplace app inventory and remediation plan: which apps have Cloud versions, which have feature gaps, which can be replaced by native Cloud functionality, and which require migration tooling or rebuild. We surface this early so your team isn't surprised mid-migration by a missing capability.

Yes — JSM implementations for IT operations and ITSM teams are one of our core engagement types. A typical IT JSM build includes service portal design, request types and forms, queues and SLAs, approval workflows, knowledge base structure, integration with email and chat, change management, problem management, incident management, and operations-level visibility. We can deliver this as a phased rollout or a single end-to-end implementation depending on your operational tolerance for change.

Absolutely. JSM is increasingly the platform organizations use for any internal service team that takes structured requests — HR for onboarding and employee tickets, Legal for contract intake, Facilities for workplace requests, Operations for procurement, Finance for expense exceptions. We design these "enterprise service management" instances with templates, request type taxonomies, approval routing, and reporting that fit non-IT workflows without forcing those teams to think like IT.

Atlassian Assets (formerly Insight) is a flexible asset and configuration management database that ships with JSM Premium and Enterprise. You should care about Assets if you need to track and relate things — laptops, servers, applications, vendors, licenses, contracts, employees, locations — and reference them from inside Jira issues. Assets is most valuable for IT teams running ITSM, but we have built useful Assets schemas for HR (employee equipment lifecycle), procurement (vendor catalogs), and security (application inventories with risk scoring).

Yes. Avaratak is an accredited Atlassian Training Partner. We deliver role-based training for end users, project administrators, Jira administrators, JSM agents, and Confluence space admins. Training can be standalone, bundled into an implementation engagement as a knowledge-transfer phase, or delivered as a recurring program for organizations that want to keep their internal team continuously up-skilled as Atlassian evolves the platform.

Yes. Workflow design, native Jira automation rules, and ScriptRunner-based extensions are routine work for us. Common asks include cross-issue automation, scheduled actions, complex approval routing, JQL-driven dashboards, and Groovy-scripted listeners for behavior that goes beyond the native automation engine. We are equally comfortable building it for you or training your administrators to build and maintain it themselves.

Most engagements start with a no-cost discovery call to understand your environment, goals, and constraints. We follow that with a written scope of work that defines deliverables, hours, fixed fees or rate, and timelines. Engagements run as fixed-fee for well-defined work (migrations, implementations, training programs) or as time-and-materials for advisory and ongoing optimization. Every engagement has a named senior consultant and a clear escalation path — you will know who is accountable, every day.

Yes, and we recommend it. Atlassian environments are living systems — features ship, teams evolve, processes drift. We offer monthly retainer arrangements that bundle a fixed number of advisory and tactical hours per month, giving your internal team a senior partner to call when something breaks, when Atlassian releases something interesting, or when a new department wants to onboard onto Jira or Confluence.

The fastest path is to book a 30-minute discovery call directly through our scheduling link or to reach out through our contact page. Bring whatever you have — a vague idea, a detailed RFP, an inherited mess, an upcoming renewal date. We'll listen, ask hard questions, and either propose an engagement or tell you honestly that you don't need one. Our goal is for the first conversation to be useful even if you never hire us.