Skip to content
Ordolith

Adobe Experience Manager

An AEM platform that stays current.

Service packs, version upgrades and the move to AEM as a Cloud Service, planned, tested and carried out without stopping your editors.

Sites › Products › HardwareIn review

Publish
Edited by Content teamSample data

Who it's for

Digital and marketing teams on Adobe Experience Manager whose platform has fallen behind, or who are planning the move to the cloud.

Sound familiar?

  • Upgrades put off for years

    Every release adds risk, and nobody wants to be the one who starts.

  • Custom code nobody trusts

    Components and workflows written years ago, which may or may not survive an upgrade.

  • The cloud move feels too big

    The deadline is set, but the plan isn't.

How the work moves

From the first message to done.

  1. 01

    Assessed

    Your code, content and configuration checked against the target version.

  2. 02

    Planned

    What changes, in what order, and how editors keep working.

  3. 03

    Code brought up to date

    Deprecated APIs replaced and custom code refactored.

  4. 04

    Content moved

    Content and assets moved and checked.

  5. 05

    Tested

    Authoring, publishing and performance tested with your team.

  6. 06

    Switched over

    Go-live planned around your calendar, with a way back.

What it includes

Included

  • An assessment of your code and configuration.
  • A written upgrade or migration plan.
  • Code updated for the target version.
  • Content and asset migration.
  • Dispatcher and pipeline setup.
  • Testing with your editors before go-live.

Optional extras

  • Components moved onto Core Components.
  • Authoring improvements while we're in there.
  • Ongoing support after the move.

What changes

Scope

In scope

  • The upgrade or move, its plan and its testing.
  • The code and configuration we own during the project.
  • The handover to your team.

Scoped separately

  • A site redesign.
  • New features beyond the upgrade.
  • Adobe licences.
A bank’s corporate websiteLeading AEM as a Cloud Service projects for a bank in Southeast Asia.Read the case study

Written by our CEO

Timeline and price

Quoted after discovery

Discovery: A free intro call first. Then $250, credited in full to the build if you go ahead.

How a project runs, and when you pay

Start with one conversation

Tell us what you need built, connected or looked after, and we'll reply with how we'd approach it.

  • Fixed scope, agreed up front

    You approve what's built and what it costs before work starts.

  • You own what we build

    Source code and documentation are handed over at launch.

  • Working across time zones

    We work with clients worldwide and keep regular overlap with your business hours.

  • Support after launch

    Optional ongoing support, agreed separately.