Jira Cloud migration — integrations & workflows Consultant
Job Title: Role: Jira Cloud migration — integrations & workflows ConsultantLocation: Remote, USAStart: ASAPRate: $80-$90 per hour depending on experienceDuration: 6 months extendableAbout SkillNet SolutionsSkillNet Solutions, Inc. is a leader in modern commerce, delivering consulting, AI solutions, and technology services to enterprises undergoing digital transformation. By implementing cloud and SaaS applications, SkillNet helps clients adapt to evolving consumer behaviors and build seamless client journeys across B2B, B2C, and B2B2C markets.Since its founding in 1996, SkillNet has partnered with industry leaders such as Oracle, Salesforce, AWS, and others to modernize operations, accelerate agility, and enhance digital and in-store experiences. With solutions delivered across 63 countries for global enterprises including Disney, lululemon athletica, and PayPal, SkillNet continues to redefine what’s possible in unified commerce and retail transformation.Position SummarySkillNet is seeking a Jira Consultant to support migration of custom integrations and automation from our current Jira setup to Jira Cloud. Work is DevOps-heavy: assess, redesign where needed, migrate, test, and cut over integrations that depend on Jira (APIs, webhooks, apps, CI/CD, internal tools). Minimum Experience: 6+ yearsMust-have skillsJira Cloud vs. Server/Data Center differences — what breaks or changes in Cloud (APIs, permissions, apps, webhooks, automation).Jira REST API v2/v3 — authentication (API tokens, OAuth where applicable), pagination, rate limits, migration of scripts/cron jobs that call Jira.Webhooks & automation — mapping Server automation (e.g. listeners, ScriptRunner, post-functions) to Jira Cloud automation, Forge/Connect app constraints, or external orchestration.CI/CD & tooling — updating pipelines, secrets, and config that reference Jira URLs, credentials, or issue keys (e.g. GitHub/GitLab/Jenkins/Azure DevOps + Jira).Identity & access — SSO/Atlassian Access concepts, service accounts, scoped tokens, least-privilege for integrations.Migration planning — runbooks, dry runs, rollback thinking, communication with app owners, and evidence-based testing (not just “smoke test one ticket”).Strongly preferredHands-on participation in at least one Jira Server/DC → Cloud (or major Cloud consolidation) project.ScriptRunner, Automation for Jira, or similar — knowing what cannot move 1:1 to Cloud and how to replace it.Observability — logging/monitoring for integration jobs after cutover.