Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  1. Fotoware Alto
    • 11.14 Schreckhorn
    • Terminology
    • Solutions
    • User Guide - Deutsch
    • User Guide - English
    • API Changelog
  2. Fotoware Veloz
    • Managing users and groups
    • Configuring archives
    • Configuring workflows
    • Configuring site behavior
    • Navigating and searching to find your assets
    • Working with your assets
    • Editing asset metadata
    • Uploading files
    • Version Control in Fotoware
    • Albums - Creating and sharing collections
    • Placing assets in a CMS
    • Working with the Fotoware Pro interface
    • Using the Fotoware plugins
    • Consent management
    • User guide to FotoWeb for iPad (Legacy)
    • Picture conferencing with FotoWeb Screens (Legacy)
    • What's what in Fotoware
    • GDPR
    • Fotoware Veloz releases
    • Activity Exports
    • Fotoware Example Workflows
  3. Fotostation
    • Getting started with Fotostation
    • Viewing, selecting and sorting files
    • Managing your assets with archives
    • Adding metadata to assets
    • Searching for assets
    • Working with your assets
    • Version Control in Fotostation
    • Automating tasks with Actions
    • Configuring metadata fields and editors
    • Configuring Fotostation
    • Configuring Fotostation for multi-user environments
    • Troubleshooting Fotostation
  4. Fotoware Flow
    • What is Flow?
    • Getting started
    • Flow dictionary
  5. Fotoware On-Premises
    • Getting started
    • Index Manager
    • FotoWeb
    • Color Factory
    • Connect
    • Operations Center Guide
  6. Integrations and APIs
    • The Fotoware API
    • Creating integrations using embeddable widgets
    • Authorizing applications using OAuth
    • Auto-tagging
    • FotoWeb Drag and Drop export
    • Integration using webhooks
    • Optimizely and Episerver plugin documentation
    • User Interface Integrations
  7. Fotoware Mobile
    • User guide for Fotoware Mobile for iPhone and Android
    • User guide to FotoWeb for iPad (Legacy)
    • User guide to FotoWeb for iPhone and Android (Legacy)

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Support
  • Home
  • Fotoware On-Premises
  • Color Factory
  • Building workflows using Color Factory (On-Premises)

Automating the migration of content from an old system into Fotoware

11. April 2025

Elaine Foley

The implementation of a fully functional DAM system often involves migrating files from various locations and organizing them in a folder structure before additional processing can be applied. 

In such a scenario, some challenges are quite common and can be overcome using various workflow features in Color Factory

  • Both high resolution and low resolution copied of images in the system can be stored in the same folder structure, and doing a manual extraction is often not doable because of the sheer volume.
  • Files may not have naming conventions in place, making it even harder to tell which version is which
  • Files may be stored on multiple servers, and your aim is to centralize this and place it in a meaningful structure

Assuming you have an existing system that holds information about what all the assets in the system are, it will often be possible to migrate from the old system to the new using Color Factory's Job Request Files (JRF). JRF files are text files with instructions to Color Factory about which files to process and which processing to apply.

  • First off you will need to export the network path (UNC) of the assets from the old system from which the migration is being made.
  • With software such as SQL server, Microsoft Excel, FileMaker or other solutions, it is often very straightforward to create a JRF file per asset in the system and drop this into a Color Factory folder.

A JRF file can for example look like this:

[JRF]
M_VERSION=2
M_INPUT_FILE=C:\Fotoware server\10 DAM filer\Historia\SSMD000731S.jpg
M_OUTPUT_FILE=C:\ColorFactory folders\01 Images output folder\SSMD000731S
M_REMOVE_INPUT_FILE=0
M_SET_EXTENSION=1
M_RETURN_PRF=0
O_INPUT_UID=85DFEBBF867A464E 93D17497CF4B1912

As the JRF is stored in Color Factory's channel input folder, all assets will be fetched and moved to the desired folder one by one (one file per JRF file) in a very controlled manner. This technique has proven successful even for extremely large collections of assets.

This process can be used for all types of assets - it's not limited to images.

Tip: Learn more about the functionality of JRF files by clicking here.

 
 
automated migration content transfer

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • Content Relation Items Changed Condition
  • Mapping of metadata category codes
  • Installing Index Manager
eco-lighthouse-miljøfyrtårn

Company

  • About us
  • Resellers
  • Careers
  • Contact us

Help & support

  • Support center
  • Consultancy
  • Tech partners
  • Fotostation
  • System status

Trust Center

  • Legal
  • Security
  • Sustainability & ESG

Locations

Fotoware AS (HQ)
Tollbugata 35
0157 OSLO
Norway
FotoWare Switzerland AG
Industriestrasse 25
5033 Buchs (AG)
Switzerland

Copyright 2025 Fotoware All rights reserved.

  • Terms of service
  • Privacy policy
  • Cookie policy

Knowledge Base Software powered by Helpjuice

Expand