Migrating Sounds from an Older KRONOS to the KRONOS 3

Narf
Jun 15
4 min read

Migrating Sounds from an Older KRONOS to the KRONOS 3

A Practical Step-by-Step Guide for Longtime Users

If you’re upgrading to the KRONOS 3 from an older KRONOS, you’ve probably noticed that some of your Programs and Combis don’t load properly. This guide breaks down everything you need to know about safely migrating your sounds to the new system.

SECTION 1 – Start With a Day-One Backup

Before making any changes, save a backup of your KRONOS 3 in its original state. This gives you a reliable factory restore file.

To save your Day-One PCG:

Insert a USB drive
Press Disk
Create or select a folder for PCG backups
Open the folder
Go to the Save tab
From the dropdown, choose Save PCG
Name the file: KRONOS 3 Day One

SECTION 2 – If You’re Migrating from a KRONOS 1

This is the simplest scenario. Just save your PCG file on the KRONOS 1 to a USB drive and load it directly into your KRONOS 3.

As long as your data only uses internal factory Programs and doesn’t reference any paid EXs libraries or custom sample data, it’s a straightforward PCG swap.

Note: This will completely overwrite the KRONOS 3’s factory content. Once you’re done with your session, simply load back your Day One PCG.

SECTION 3 – If You’re Migrating from a KRONOS 2

Best-Case Scenario

If your Programs live only in U-G, U-FF, and U-GG, follow this method:

Save a PCG on your KRONOS 2 with just those Program banks selected
Load that PCG into your KRONOS 3
Manually reassign any Combis to reference their new Program locations if necessary

More Complex Scenario

If your sounds are in banks now used by the KRONOS 3 factory preload (like U-CC, U-DD, U-EE,), you have three choices:

Remap banks ahead of time using PCG Tools (Windows only)
Load your Programs into available user banks (U-G, U-FF, or U-GG) and manually update Combis afterward
Overwrite KRONOS 3’s banks with your own and manage different setups using PCG files per session

Just remember: the internal memory can be overwritten. Use PCG files like session templates and swap them as needed.

SECTION 4 – RAM and Sample Data Management

KRONOS 3’s factory preload uses up most of the sample RAM, leaving only about 73 MB free.

If your soundset uses user samples, Korg-purchased EXs libraries, or third-party content, you’ll need to unload some of the factory KSC.

How to unload the factory preload and selectively add EXs:

Go to Global Mode > KSC AutoLoad
Uncheck the box for PRELOAD.KSC to unload the full factory KSC
Press Add KSC
Navigate to:
Factory > Preload_Individual_KSC
Select the EXs you want to include, either one at a time or by using Multiple Select
Press ADD
Once all required KSCs have been added to the KSC Autoload Page, Press Do AutoLoad Now

This gives you finer control over RAM usage and lets you prioritize only the EXs you need.

What EXs Do You Actually Need?

For KRONOS 1 and 2 users, here are the key sample sets:

EXs1–9 – Native to KRONOS 1 and 2
EXs17–18 – Added in KRONOS 2
EXs22 – Italian Grand, included in the KRONOS SE
EXs23, EXs206–218 – New to KRONOS 3, supports expanded Programs in U-CC and U-DD

If you’re not using Combis or Programs that rely on the new content, you don’t need to load it—freeing up RAM for your own data.

SECTION 5 – Managing Conflicting Program Banks

If your KRONOS 1 or 2 data uses Program banks now filled with KRONOS 3 factory sounds, those won’t coexist.

Options:

Overwrite KRONOS 3’s internal content and load your older PCG
Save KRONOS 3’s Day One PCG first, then restore it when needed
Create separate PCG files for different band setups or gigs and load them per session

The memory structure is flexible—think of PCGs as project files.

SECTION 6 – THINKING IN SESSIONS

You can’t have every sound loaded at once.

That’s just the nature of working with limited RAM and fixed Program bank slots on the KRONOS 3.

Instead, treat each PCG file as its own session.

Load what you need for a specific gig, rehearsal, or project—and switch as needed.

The more consistent your method for organizing and swapping these PCG files, the easier it’ll be to stay in control and avoid conflicts down the line.