Frequently asked questions.

An Atlassian Solution Partner is a company recognized by Atlassian to provide services across its products, including Jira, Jira Service Management, Confluence, and Assets. Avaratak's Atlassian consulting practice is staffed by senior consultants with at least five years of hands-on Atlassian experience. Separately, Avaratak has a dedicated Claude consulting practice staffed by expert senior consultants with extensive software development experience.

Avaratak has two independent practices. As an Atlassian Solution Partner, we help organizations with Jira, Jira Service Management, Confluence, Assets, Cloud migrations, governance, licensing, integrations, and training. Our Claude practice delivers Claude Code rollouts, custom agents, MCP integrations, enterprise adoption, workflow automation, AI evaluation, governance, and training. You can engage either team independently; using Claude with Atlassian is an option, not a requirement.

Three differences apply to both practices. First, you work directly with expert senior consultants: Atlassian practitioners with at least five years of hands-on Atlassian experience, or Claude specialists with extensive software development experience. Second, we agree scope, rates, and billing terms before work begins, without handing delivery to a junior team. Third, we put the client's interests first: if an existing approach is sufficient or an initiative is not worth pursuing, we will say so.

Avaratak is based in Plover, Wisconsin and works remotely with organizations across the United States. Claude and Atlassian projects typically use video working sessions, shared planning materials, and appropriately scoped access to your systems. We can also travel for kickoffs, executive briefings, and on-site training when the engagement calls for 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 and updated by Atlassian, while Data Center is self-managed and provides direct infrastructure control. Atlassian Server is retired. Atlassian has announced March 28, 2029 as the end-of-life date for affected Data Center products, including Jira Software, Jira Service Management, and Confluence. Some customers may qualify for limited, exception-based extensions. Bitbucket and Bamboo Data Center have a separate continuation path through the Bitbucket Hybrid License for eligible existing customers. Organizations should assess product dependencies, security and data requirements, Marketplace apps, integration risks, and the time needed for a validated Cloud transition.

No. Partner pricing matches Atlassian's published pricing — Atlassian compensates partners through the channel rather than by marking you up, so the number on your quote is the number you would see buying direct. What changes is everything around it: someone tracking renewal dates before they ambush you, modeling the cost of a tier change before you cross it, consolidating scattered product and app renewals onto a single quote, and escalating through partner channels when a support ticket stalls. You also do not have to buy consulting from us in order to buy licensing through us.

Access, not activity. Atlassian bills for every user granted product access — whether assigned directly or inherited through a group — regardless of whether they have logged in this year. The person who left in 2024 but still sits in a jira-software-users group is a paid seat. Deactivating the account frees it; inactivity alone does not. Jira Service Management is the exception worth knowing: you license agents, while portal customers raising and tracking requests are unlimited and free. A group-membership audit before renewal is the single most reliable place we find money.

Yes, and it surprises almost everyone. Atlassian requires each Marketplace app to be licensed at the same user tier as the product it runs on. If Jira is licensed for 250 users, every app is licensed for 250 users — including the one four people actually open. It also means crossing a tier boundary reprices your entire app portfolio at once, not just the host product. That is why app rationalization is part of every licensing review we run: which apps earn their tier-wide price, and which have quietly been replaced by native functionality.

Usually, yes. Atlassian supports co-terming, so products and Marketplace apps bought at different times can be aligned to one renewal date, with the difference prorated at the point of alignment. The payoff is mostly administrative: one renewal conversation, one purchase order, one budget line, and no trickle of unexpected invoices across the year. It also makes tier planning coherent, because you are sizing the whole estate at a single moment instead of guessing product by product. As your partner of record we handle the mechanics and hand you the calendar.

Guard Standard (formerly Atlassian Access) adds organization-wide identity and security controls across every Atlassian Cloud product you own: SAML single sign-on, enforced two-step verification, SCIM provisioning and deprovisioning from your identity provider, API token controls, and data security policies. You probably need it if you have compliance obligations, an existing identity provider like Okta or Entra ID, meaningful staff turnover, or an auditor who asks how access gets revoked. You probably do not if you are small, low-risk, and comfortable managing access by hand. It bills per unique user across your organization, so cost tracks your identity footprint rather than your product count.

It depends on what is actually hurting. Premium's differentiators are operational: a 99.9% uptime SLA, unlimited storage, sandbox and release-track environments for testing changes before they reach production, deeper admin controls, and higher automation limits — plus product-specific additions like Assets in Jira Service Management and analytics in Confluence. If you change configuration frequently, run regulated workloads, or keep bumping into automation limits, Premium usually pays for itself in avoided incidents. If your instance is stable and lightly customized, Standard is often the honest answer, and we will say so.

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 pricing depends on the systems involved, complexity, and expected effort. We agree rates and billing terms in a written scope before work starts. 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.

The senior consultant who scopes your engagement remains accountable through delivery. Atlassian projects are handled by senior practitioners with at least five years of hands-on Atlassian experience. Claude engagements are handled by expert senior consultants with extensive software development experience. We do not hand your project to a junior team or use client work as on-the-job training. You know who is assigned before agreeing to the scope.

The least that gets the job done. Assessment and advisory work often needs no more than read access plus a look at your admin configuration. Implementation, migration, and automation work generally needs product or site admin. We work within your onboarding requirements — NDAs, background checks, access reviews — use named accounts rather than shared credentials so every change is attributable in the audit log, and expect access to be revoked when the engagement closes. If your security team wants a written access justification, ask for it; we would rather document it than debate it.

That describes most of our engagements. Internal admins rarely need replacing — they need air cover for a decision, a second opinion on an architecture, or a specialist for the thing they have never done before: an instance merge, a Cloud migration, an Assets schema, a workflow scheme that has quietly become load-bearing. We transfer knowledge as we go and document what we build, because an admin who can maintain the work is a client who calls us about interesting problems rather than ones we created.

Yes. Changing your partner of record is an administrative step taken at renewal — your licenses, data, and instance are untouched, and no migration is involved. If you are mid-term, we can plan the change for your next renewal cycle. We will also say the unglamorous thing: if your current partner is serving you well, staying put is the right call, and we would rather tell you that than win an account we cannot meaningfully improve. Switching should be about the service you are getting, not the logo on the invoice.

Yes. Not every problem needs a major program. Short Atlassian engagements can include a Jira or Confluence health check, a licensing review, or an automation repair. Claude work can begin with an architecture second opinion, an AI-readiness assessment, an agent evaluation, or hands-on engineering office hours. Small projects get the same senior attention and written scope as larger projects, and sometimes our recommendation is simply to change three things and stop.

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, estimated hours, rates, billing terms, and timelines. Every engagement has a named senior consultant and a clear escalation path — you will know who is accountable, every day.

Yes. We can scope ongoing senior support for either practice. For Atlassian, that may mean governance, administration, platform changes, and new team onboarding. For Claude, it can cover model and tool updates, agent evaluations, workflow improvements, and engineering enablement. Support terms and hours are agreed upfront; we recommend it only when your team benefits from continued help.

You hear about it before it happens, not on the invoice. Every engagement carries a written scope, and when something outside it surfaces — an undocumented integration, a Marketplace app with no Cloud path, a stakeholder group nobody mentioned in discovery — we stop, quantify the impact, and put the options in front of you in writing. You can approve a change order, defer the work to a later phase, or decline it entirely. Surprise invoices are how consulting firms lose clients; we would rather keep ours.

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.