Digital Asset Management Platform Support & Data Migration

Azati became the sole technical partner for a global beverage enterprise with no internal AEM engineering capacity, resolving platform issues, customizing Adobe Experience Cloud for regional workflows, and ultimately designing a reusable migration pipeline that transferred 10,000+ digital assets and metadata records to a new DAM vendor in under two months.

Discuss your project
10,000+

digital assets migrated with full metadata integrity

1.5 years

of continuous platform support and customization

2 months

to complete end-to-end market migration

Technologies used

Java
Java
JavaScript
JavaScript
AWS
AWS
Adobe AEM
Adobe AEM
Amazon S3
Amazon S3
Adobe Experience Cloud
Adobe Experience Cloud

Motivation

The client, a global beverage company with 30,000+ employees, had no dedicated internal technical team to manage and customize their Adobe AEM-based digital asset management platform. Their marketing operations relied on a centralized DAM system for brand imagery, product visuals, and campaign materials used across regional markets.

Without technical ownership, customization requests stalled, Adobe support tickets went unmanaged, and the eventual migration to a new DAM vendor had no clear execution path. Azati stepped in as the technical partner to own all of this, from daily platform support and AEM customization to designing and executing the final large-scale data migration.

Main challenges

Challenge 01

No Internal Technical Ownership for a Business-Critical Platform

The client's digital assets division operated without a dedicated engineering team, despite running a platform that marketing teams across multiple regional markets depended on daily. Customization needs, integration work, and Adobe support escalations required specialist expertise in Adobe AEM and the broader Adobe Experience Cloud, expertise the client did not have in-house. Every unresolved ticket and delayed customization had a direct downstream effect on marketing operations.

#1
Challenge 02

Inconsistent Data and API Gaps During Migration

When migration work began, the team encountered significant data integrity issues: API responses from the client's endpoints did not match the provided template files, file extensions retrieved via the API were incorrect, and some assets were entirely absent from the API. Each discrepancy required alternative approaches, direct coordination with the client's engineering team, and iterative adjustments to the ingestion logic, adding complexity and timeline risk to what initially appeared to be a straightforward migration.

#2
Challenge 03

Building a Scalable Pipeline Across Multiple Markets

The ingestion pipeline had to handle large volumes of assets with complex, multilayered metadata, including regional filters, access policies, and duplicate management rules. Large files required a separate endpoint and ingestion path. Critically, the solution had to be built not as a one-off script but as a reusable, market-agnostic pipeline capable of serving additional regional markets beyond the initial Swiss rollout without rebuilding from scratch.

#3

The client's requirements

The client needed a technology partner with hands-on Adobe AEM expertise to step in and own all technical operations for their DAM platform, then transition that knowledge into a clean, scalable migration to a new vendor. Specifically:

  • Manage and resolve incoming support tickets for the Adobe AEM platform on an ongoing basis
  • Liaise with Adobe's official technical support on complex escalations requiring vendor coordination
  • Implement platform customizations to adapt the system to internal business workflows and regional requirements
  • Develop and execute a migration pipeline to transfer 10,000+ digital assets and metadata from Adobe AEM to the client's new proprietary platform
  • Ensure all migrated assets preserved their metadata structure, including regional access policies, collections, filters, and content attributes
  • Build a reusable migration solution extensible to other regional markets beyond the initial scope

Why Azati?

End-to-end delivery with embedded project management

The engagement required both deep technical execution, custom Groovy scripting, Java development, API integration, and structured project management. Azati provided both, with a BA/PM embedded in the team to coordinate daily communication, manage timeline risks, and keep the client continuously informed throughout both phases of the project.

Flexible subcontracting for specialized depth

Where additional Adobe AEM specialization was needed beyond the core team's capacity, Azati brought in vetted subcontractors with direct AEM development experience. This ensured the team always had the right expertise available without overextending the permanent team or compromising delivery timelines.

Long-term partner, not a one-time vendor

The relationship began with a support engagement and evolved into a critical migration project, precisely because Azati operated as an embedded partner rather than a transactional vendor. The team adapted as the client's needs changed, from routine ticket resolution to architecting and executing a full platform transition.

Need a reliable partner for DAM support or migration?

Whether you're managing a complex Adobe AEM environment or planning a migration to a new platform, Azati can own the technical execution end to end.

Let's discuss your project

Solution

01

Adobe AEM Platform Support & Customization

Azati provided continuous technical support for the client's Adobe AEM-based DAM platform, handling incoming requests through the client's Kanban backlog and managing escalations to Adobe's official support team. The team implemented targeted customizations to the platform's asset authoring layer, including Adobe Brand Portal and Adobe Dynamic Media, adapting the system to regional business requirements, user group policies, and metadata governance rules.

Key capabilities:
  • Day-to-day resolution of platform support tickets via client backlog
  • Adobe support escalation management and ticket accompaniment
  • Customization of AEM asset authoring workflows and metadata schemas
  • Maintenance of access policies, user groups, and regional content governance
02

Custom Data Migration Pipeline

When the client decided to move away from Adobe AEM to a new DAM vendor, Azati designed and built a custom migration pipeline to transfer all digital assets and associated metadata to the new platform via Amazon S3. The pipeline handled the full complexity of the client's asset library, including images with multilayered metadata, regional tagging, and access control attributes, resolving API inconsistencies and data gaps encountered during development.

Key capabilities:
  • Custom ingestion scripts in Groovy/Java for metadata extraction and transformation
  • Template files used as source of truth to resolve API data inconsistencies
  • Asset transfer pipeline via Amazon S3 to the client's new proprietary platform
  • Separate ingestion logic for large files via dedicated endpoint
03

Metadata Mapping & Verification

Every migrated asset underwent structured verification to confirm that metadata was correctly mapped and transferred to the new platform. The mapping logic was developed to handle inconsistencies in source data, including missing fields, format differences, and template file variations, with the team iterating on the ingestion script as new edge cases were discovered during the migration run.

Key capabilities:
  • Structured metadata mapping from Adobe AEM schema to target platform schema
  • Verification of all migrated assets for correctness before handoff
  • Iterative adjustment of ingestion scripts as template inconsistencies emerged
  • Documentation of mapping rules for ongoing reuse across markets
04

Reusable Migration Architecture

The migration tooling was deliberately architected as a reusable, market-agnostic solution, not a one-off script. The ingestion pipeline was designed to support additional markets beyond the initial Swiss rollout, with the same core logic extensible to new datasets, metadata schemas, and regional configurations. This gave the client a scalable technical asset that outlasted the engagement itself.

Key capabilities:
  • Market-agnostic ingestion script configurable per dataset and region
  • Metadata mapping logic reusable across asset types and market configurations
  • S3-based transfer layer independent of source platform specifics
  • Pipeline extensible to all client markets without architectural rework

Major achievements

Metric / areaBefore engagement with AzatiAfter engagement with Azati
Technical platform ownershipNo internal AEM teamDedicated Azati team handling all platform ops
Adobe support escalationsUnmanaged, no technical liaisonActively managed and resolved
Platform customizationBacklogged, no execution capacityDelivered continuously via Kanban
Asset migrationManual, time-prohibitive at scaleAutomated pipeline, 10,000+ assets migrated
Metadata integrityAt risk without structured tooling100% of assets verified post-migration
Migration reusabilitySingle-market, ad-hoc approachReusable pipeline, extensible to all markets

Security

The platform operated under SSL encryption with two-factor authentication enforced for all user access. During the migration phase, all assets and metadata were transferred via Amazon S3 with access policies aligned to the sensitivity of the client's brand and regional marketing data. The full engagement was conducted under a signed NDA, with the client identity remaining confidential.

Engagement & delivery

T&M model throughout both phases

Both the support engagement and the migration project operated on a Time & Material basis, providing the client with full flexibility to scale effort based on active workload and project phase, reactive support when needed, full migration team when the transition began.

Kanban-driven execution aligned to client backlog

Work was organized around the client's own backlog. The team pulled tickets continuously, prioritized by client input, and delivered in a steady cadence suited to the mix of reactive support work and proactive development:

  • BA/PM as primary client contact for all coordination and communication
  • Daily progress updates during migration when timeline risks emerged
  • Subcontractor expertise integrated within the Azati delivery model where needed
  • Verification step embedded as a formal gate before migration sign-off

Results & business impact

Operational Continuity

The client's DAM platform remained fully operational throughout the engagement. Support requests and platform customizations were handled without gaps, ensuring marketing teams were never blocked on asset access or platform tooling.

Clean Migration, No Data Loss

All 10,000+ digital assets and their associated metadata were successfully transferred to the new platform, with every asset passing a structured verification step before handoff.

Reusable Technical Asset

The ingestion pipeline built for the Swiss market migration was architected for reuse across all client markets, a working, documented tool that outlasted the engagement itself.

Accelerated Platform Transition

What would have required extensive manual effort, analyzing each image, extracting and mapping metadata, validating the transfer, was reduced to an automated, structured process completed within a two-month timeline.

Embedded DAM Domain Expertise

Azati's team developed deep expertise in digital asset management for the beverage industry: collections, metadata hierarchies, duplicate management, and regional access governance, embedded in the tooling and documentation left with the client.

Strategic wins

The engagement delivered lasting value beyond the immediate project scope:

Template-as-truth pattern for unreliable APIs

Faced with inconsistent API data during migration, the team established a reusable pattern, using client-provided template files as the authoritative metadata source rather than relying on API responses. This approach cleanly resolved data integrity issues and is directly applicable to future migrations where API data quality is uncertain.

API team coordination as a project success factor

The migration revealed that API team availability in the early project phase is critical to timeline predictability. Delays in receiving corrected endpoints added time that could have been avoided. This lesson is now embedded in Azati's migration project setup, API access and support availability are scoped and confirmed before work begins.

From single-market script to platform-agnostic pipeline

Rather than building the minimum to migrate Swiss market assets, the team invested in a reusable architecture. The ingestion script handles variable file sizes, multiple metadata schemas, and different endpoint configurations, making it a genuinely transferable asset for the client's remaining markets.

Structured verification as a delivery standard

Embedding a formal asset verification step, rather than assuming successful transfer, caught mapping errors before they reached production. This verification-first approach is now part of Azati's standard migration delivery model for all future data migration projects.

Team composition

Two focused, lean teams covered the full engagement, a support team embedded for 1.5 years, and a dedicated migration team that executed the platform transition in 2 months.

  • BA / Project Manager (support phase) served as the primary client contact, managed the Kanban backlog, coordinated Adobe support escalations, and ensured continuous alignment between client priorities and delivery.
  • Java / Adobe AEM Developer ×2 (support phase) handled platform customizations, Groovy scripting, AEM workflow development, and day-to-day ticket resolution across the 1.5-year engagement.
  • BA / Project Manager (migration phase) owned project coordination, daily client communication, progress reporting, and the formal verification gate before migration sign-off.
  • Developer ×3 (migration phase) built and iterated on the ingestion pipeline, metadata extraction and mapping logic, S3 transfer layer, API integration, and large-file handling, delivering a fully verified, reusable migration solution within a two-month timeline.

Last updated

Got a job for Azati? Let’s talk business!

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

What's next?

  • 1. Tell Us Your Story
    Share your project details. We'll connect within 24 hours and ensure confidentiality with an NDA.
  • 2. Get Your Roadmap
    Receive a detailed proposal with scope, team composition, timeline, and costs tailored to your goals.
  • 3. Start Building
    Azati aligns on details, finalize terms, and launch your project with full transparency.