Atlassian Cloud migration on SHIP-HATS for Singapore Government agencies.

Information Officer is a certified Atlassian Solution Partner in Singapore that helps government agencies plan and execute their migration to Atlassian Cloud on SHIP-HATS — the CI/CD and project management component of the Singapore Government Tech Stack (SGTS), managed by GovTech.

Whether you are migrating from a self-managed Atlassian environment, or evaluating the Shared versus Dedicated Atlassian model for your agency, we provide the technical expertise and hands-on delivery to get it right.

Atlassian tools available on SHIP-HATS

SHIP-HATS includes the core Atlassian product suite — procured through GovTech, integrated with TechPass, and configured to meet Singapore Government IM8 compliance requirements.

Jira on SHIP-HATS

Jira

Project and issue tracking for government software delivery teams — agile boards, backlogs, sprints, and reporting, integrated with GitLab and TechPass.

Confluence on SHIP-HATS

Confluence

Team knowledge base and documentation — structured spaces, decision logs, and technical documentation that stays connected to work in Jira.

Jira Service Management on SHIP-HATS

Jira Service Management

Government IT service desk with SLA management, change approvals, and service portals — for both internal IT teams and citizen-facing services.

Shared or Dedicated

Choose the centrally managed Shared site, or a Dedicated site with full site admin rights, custom plugins, and flexible configuration for more complex agency needs.

Our SHIP-HATS Atlassian services

End-to-end Atlassian migration and configuration for Singapore Government agencies onboarding to SHIP-HATS from initial assessment through to production cutover and team enablement.

Migration Assessment & Planning

Assess your current Atlassian environment — Server, Data Center, or self-managed Cloud — map dependencies and data volumes, and produce a phased migration plan aligned to your agency's operational constraints.

Shared vs Dedicated Evaluation

Evaluate your agency's requirements — workflows, plugins, site-level settings, and compliance needs — against the SHIP-HATS Shared and Dedicated models, and recommend the right onboarding path.

Migration Execution

End-to-end migration of Jira projects and issues, Confluence spaces and pages, JSM service desks, users, permission schemes, and existing integrations — with data integrity validation before cutover.

SHIP-HATS Configuration

Configure Atlassian tools within SHIP-HATS to your agency's workflows — custom issue types, screens, workflows, service catalogs, automation rules, and IM8-aligned access controls and permission schemes.

Plugin & Marketplace Advisory

Identify which Marketplace plugins work within the SHIP-HATS Shared model and which require the Dedicated model. We advise on plugin selection, Shared model implications, and help you with migration.

Training & Adoption

Train Subscription Admins, project administrators, and end users on SHIP-HATS-specific workflows, TechPass authentication, Equip provisioning, and best practices for operating within the WOG environment.

Ready to migrate your agency to SHIP-HATS?

Our certified Atlassian consultants in Singapore can help you nagivate the SHIP-HATS environment and government compliance requirements. Let's start with a migration assessment.

How we work

A structured delivery approach that minimises disruption to live government operations — validating data integrity and user access at every stage before cutover.

  1. 1

    Assess

    We review your current Atlassian setup — products in use, user base, data volumes, integrations, custom configurations, and Marketplace plugins. We identify what maps cleanly to SHIP-HATS and where additional planning is needed.

  2. 2

    Recommend

    We recommend the right SHIP-HATS model (Shared or Dedicated), migration path, and phasing strategy. We produce a clear plan with timelines, responsibilities, and cutover criteria — reviewed with your agency before work begins.

  3. 3

    Migrate

    We execute the migration of Jira projects, Confluence spaces, JSM service desks, user accounts, permission schemes, and integrations — with validation runs in a staging environment before the production cutover.

  4. 4

    Configure

    Post-migration, we configure your SHIP-HATS Atlassian environment to your agency's workflows — issue types, workflow schemes, permission models, service catalog, automation rules, and IM8-aligned access controls.

  5. 5

    Enable

    We train Subscription Admins and end users, hand over documentation, and provide a hypercare period post-cutover — so your agency is confident managing the SHIP-HATS environment independently.

image

Our Offices

We maintain a strong global presence with offices in California, New York, and Singapore, enabling us to deliver seamless, localised support and strategic solutions across key markets.

Singapore

Information Officer Pte Ltd
1002 Jalan Bukit Merah #06-19
Singapore 159456
+65 8086 7376 (WhatsApp)

San Fransisco, California

Information Officer LLC
PO Box 5021
Berkeley, California 94705, USA
+1 (212) 913-0469

Trusted by businesses around the world

Pentagon Technologies
Wilmar International
Edwards Lifesciences
Singapore Telecommunications (Singtel)
Housing Development Board (HDB) Singapore
Gordon Haskett Research Advisors
Ngee Ann Polytechnic
MyRepublic

Our technology partners

Atlassian
HaloITSM
ONES.com
Odoo
Amazon Web Services
Kerio
Dell EMC
Dell EMC

Frequently asked questions

What is SHIP-HATS?

SHIP-HATS (Secure Hybrid Integration Platform — Harnessing All Tools Seamlessly) is the CI/CD and DevSecOps component of the Singapore Government Tech Stack (SGTS), managed by GovTech. It provides government agencies with a centralised, secure platform for software delivery — covering source code management (GitLab), project tracking (Jira), documentation (Confluence), service management (Jira Service Management), and security scanning. Over 673 government systems are currently onboarded to SHIP-HATS.

What Atlassian tools are available in SHIP-HATS?

SHIP-HATS includes Jira (project and issue tracking), Confluence (knowledge base and documentation), and Jira Service Management (ITSM and service desk). These are available under two models: a Shared model (centrally managed by GovTech, suitable for most agencies) and a Dedicated model (an agency-owned Atlassian Cloud site with full site admin rights, custom plugins, and flexible configuration).

What is the difference between the SHIP-HATS Shared and Dedicated Atlassian models?

The Shared model provides a centrally managed Atlassian Cloud environment with standard configurations and a fixed set of approved plugins — suitable for most agencies. The Dedicated model gives an agency its own Atlassian Cloud site with full site admin rights, the ability to manage their own Marketplace plugins, and custom workflows not possible in the shared environment. The Dedicated model is for agencies that need granular site control, specific plugins, or configurations the Shared model cannot support.

Which Singapore Government agencies need to migrate to SHIP-HATS Atlassian Cloud?

Government agencies and statutory boards currently running Atlassian products outside of SHIP-HATS — whether on self-managed servers, Atlassian Data Center, or standalone Atlassian Cloud tenancies — should consider migrating to benefit from centralised procurement, WOG-standard compliance, TechPass identity integration, and IM8-aligned security controls. Agencies on Atlassian Data Center are also subject to the Atlassian Data Center End of Life timeline (March 2029).

How does SHIP-HATS Atlassian differ from standard Atlassian Cloud?

SHIP-HATS Atlassian Cloud is procured and managed through GovTech, integrating with Singapore Government identity infrastructure (TechPass/SEED) and the Equip provisioning system. It is configured to meet IM8 policies and AIA (Application Infrastructure Architecture Standard) compliance requirements. The Shared model restricts certain site-level settings and plugin choices to maintain security across a multi-agency environment. The Dedicated model preserves these governance integrations while giving agencies their own site with greater administrative control.

Can we bring our own Marketplace plugins to SHIP-HATS Atlassian?

In the Shared model, plugins are centrally managed by GovTech — agencies can request additions but approvals depend on security, suitability, and cost considerations. In the Dedicated model, agencies manage their own plugins and can install Marketplace apps independently. If your agency depends on specific plugins not available in the Shared model, the Dedicated model is likely the right path. We help agencies assess which model fits their requirements.

How long does a SHIP-HATS Atlassian migration take?

A straightforward migration of a single Jira or Confluence instance with standard configuration can be completed in 4–8 weeks. A full migration involving multiple products, complex workflows, custom integrations, large data volumes, and Subscription Admin setup typically takes 8–16 weeks. We phase migrations to validate data integrity and user access before the production cutover.

Does Information Officer have experience with Singapore Government Atlassian environments?

Yes. Information Officer is a certified Atlassian Solution Partner with offices in Singapore and local employees where security clearance is required. We have experience delivering Atlassian implementations and migrations for organisations in Singapore operating under government and enterprise compliance requirements. Our Singapore-based team understands the SHIP-HATS context, GovTech procurement processes, TechPass integration, and IM8 policy constraints.

Your SHIP-HATS Atlassian migration partner in Singapore

Whether you're assessing the Shared vs Dedicated model, planning a migration from Data Center, or need hands-on configuration support — our certified Atlassian consultants are ready to help.