Book a Demo
Implementation and support

DAM Services For Launch, Migration and Support

iBase supports the practical work around a DAM project: requirements, configuration, hosting, migration, integration, training and ongoing support. The aim is to launch a system that reflects your content, users, infrastructure and day-to-day collection workflows.

iBase administration interface
Implementation covers the settings, users, permissions and workflows that make the DAM useful in daily work.
Service areas

Support from Plan to Launch

Services are shaped around your assets, metadata, users, governance needs and deployment model, so the system launches with workflows your team can actually use.

Implementation and configuration icon
Implementation

Installation and Configuration

Set up users, permissions, metadata schemas, workflows, public routes and administration settings around the way your organisation manages assets, with the scope agreed before implementation begins.

Metadata import icon
Migration

Legacy Data Import

Map files and metadata from folders, spreadsheets, text files, databases or legacy systems into structured iBase records, with validation steps to reduce risk before launch.

Hosting environment icon
Hosting

Cloud and On-Premises Hosting

Choose managed cloud hosting or deployment into your own infrastructure, with guidance around resilience, storage, access, security and platform requirements including operating system and database choices.

Integration API icon
Integration

API and Data Flows

Connect iBase with websites, collection systems, content systems, ecommerce routes or scheduled imports using an integration pattern that fits the job.

User training and adoption icon
Training

Administrators and Users

Help administrators and everyday users understand search, metadata, upload, download, permissions and administration with training focused on real tasks.

Support and service review icon
Support

Responsive Product Support

Cloud subscriptions include support, with support contracts available for on-premises clients who want assistance cover and access to discounted upgrades.

What is included in practice

What Buyers Need to Know

Implementation support is not just a handover call. The practical work can include hosting evidence, migration validation, integration planning, recorded training, administrator support and agreed support routes that continue after launch.

Cloud hosting

AWS London Hosting and Resilience

Cloud deployments can use AWS London hosting, load-balanced application servers, resilient asset storage, regular database backups and AWS versioning to help protect against accidental deletion or overwrite. Additional replication and recovery planning can be discussed where a collection needs extra resilience.

Configuration

Clear Scope Before Implementation

Installation is included as part of the iBase solution. Configuration is specified before implementation begins, so permissions, schemas, workflows, public routes and any customisation work are understood before launch.

Migration

Audit, Import and Validate

Migration can start with a review of source data, then move through mapping, import, duplicate checks, validation reports and training on the migrated structure.

Integration

API, Watch Folder and CMS Routes

Integrations can use the iBase API, flat files, scheduled imports, watch folders or two-way connections with content, commerce and collection management systems.

Training

Recorded Training Sessions

Training can be delivered by video call and screen share, recorded for later distribution and focused separately on everyday users, content managers, administrators and IT staff. Initial training is commonly split into short focused sessions so teams can absorb the main system and administration tasks.

Support

Product and Workflow Help

Support can cover product questions, configuration, workflow issues, integration needs, monitoring conversations and practical changes as the DAM settles into everyday use.

Client-hosted systems

Platform Requirements

For client-hosted deployments, iBase can provide requirements for server resources, storage, databases and deployment environments, including AWS or Azure where appropriate.

Delivery support

Start with the Collection

A good iBase project begins by understanding the content, metadata sources, audiences, publishing needs and constraints around governance or hosting.

Discovery

Requirements and Workflow Review

Clarify asset volumes, file types, current pain points, user groups, approval steps, reporting needs and the daily tasks the DAM needs to support.

Metadata

Schema and Vocabulary Planning

Shape fields, controlled vocabularies, taxonomy structures, item relationships and validation rules around the way your organisation describes content.

Governance

Permissions and Access Model

Plan roles, secure folders, metadata visibility and workflow access before users begin relying on the system.

Publishing

Public Access and Portals

Support public search, curated collections, licensing, ecommerce, multilingual routes or specialist portals where approved content needs to reach wider audiences.

Migration

Data Mapping and Validation

Move legacy material into iBase with mapping, cleansing, import and review steps that reduce risk before launch and help teams understand the new structure.

Adoption

Training and Launch Support

Prepare administrators and everyday users for the workflows they will use most, then support changes as the repository evolves.

Project approach

30+ Years of DAM Knowledge

iBase has supported museums, archives, councils, research bodies and commercial image libraries through migration, configuration, launch and long-term operational change.

01

Scope Clearly

Agree what needs to be configured, migrated, integrated and supported before implementation begins.

02

Launch Practically

Help administrators and users get comfortable with the search, upload, metadata and sharing workflows they will use every day.

03

Improve Over Time

Support changes as collections, portals, users, integrations and governance needs evolve after launch.