Support · Data Collection

Import CC Uploader Tasks into CC Sync

Move your existing CC Uploader tasks to CC Sync in one short sitting - export, import, review, resume.

Support / Data Collection / CC Sync Quick Start / Import CC Uploader Tasks

Import CC Uploader Tasks into CC Sync

The one-time move from the legacy CC Uploader to CC Sync - your tasks travel as the files the old app saves, and CC Sync tells you exactly what changed on the way.

Overview

Already running CC Uploader? CC Sync can take the tasks you built there and convert them - no need to rebuild every task by hand in the wizard. This guide walks you through the whole move: save the configuration in the old app, import it into CC Sync, and a short review at the end so you know exactly what changed.

1

Save config in CC Uploader

2

Import into CC Sync

3

Enter share credentials

4

Review the report & tasks

5

Resume

Concept · A conversion, not a copy CC Uploader and CC Sync store tasks differently. The importer converts what maps cleanly, re-matches each task's destination against your current ChromaChecker account, and lists every difference in a report. That's also why imported tasks start paused - you get to check them before they run.

Before you begin

  • CC Sync installed and logged in. Not there yet? Start with the CC Sync Quick Start.
  • Access to CC Uploader - you save the configuration there, in the old app. If the two apps live on different machines, you'll move the saved file (or files) between them; a USB stick or a network share is plenty - they're small either way.
  • Admin Lock unlocked. While task editing is locked in CC Sync, Import Legacy Tasks… is blocked (see Admin Lock).
  • Log in to the same organization your CC Uploader tasks uploaded to - during the import, CC Sync re-matches each task's destination against the account you're logged in to.

Note: if IT locked the task list in your old CC Uploader, opening the old app's Admin window in Step 1 requires that old admin password.

Step 1 · Save your tasks from CC Uploader

Every CC Uploader version does this the same way: open the Admin window and press Save Configuration. That's the last thing you do in the old app.

The screenshots below are from CC Uploader 2.1.0. On 1.0.x the windows and buttons look a bit different, but the general idea is the same - open the Admin panel and save the configuration.

CC Uploader main window with two tasks and the tools button in the bottom-left corner 1
  1. 1 Click the tools button in the bottom-left corner of the CC Uploader window. The Admin window opens.
CC Uploader Admin window with the Save Configuration button 1
  1. 1 Click Save Configuration.
Save Configuration dialog saving CCUploader Task Export.json to the Desktop 1 2
  1. 1 Keep the suggested name - here CCUploader Task Export.json - or type your own, and pick a location you'll find again (the Desktop works fine).
  2. 2 Click Save. On this version that single file now holds your whole task list. On 1.0.x you instead get one .CCT file per task, each named after the task and the moment it was saved - collect them all, none of them is optional.
Tip · Different machines? If CC Sync runs on another computer, copy what you just saved there now - all of it - and keep it together in a single folder. Everything from Step 2 on happens on that machine.

Meet the example tasks

Through this guide we'll follow two tasks built in CC Uploader - one watching a local folder, one watching a network share - so you can see exactly what the import does with each.

Example task 1 - watches a local folder
CC Uploader Task Setup window of a task watching a local folder
Example task 2 - watches a network share
CC Uploader Task Setup window of a task watching a network share via the Auto Mount tab 1
  1. 1 This task watches a network share (the Auto Mount tab) - during the import, CC Sync will ask for this share's credentials (Step 3).

Step 2 · Import into CC Sync

Over to CC Sync.

CC Sync Task Panel with the Tasks menu open and Import Legacy Tasks highlighted 1 2
  1. 1 Open the Tasks menu…
  2. 2 …and click Import Legacy Tasks…

Before anything happens, CC Sync shows a short heads-up:

Legacy Import — Please Read dialog with Continue and Cancel buttons 1 2 3
  1. 1 Read it once: not everything maps 1‑to‑1, a report will list the differences, and imported tasks start paused.
  2. 2 Optional: tick Don't show this again to skip this note on future imports.
  3. 3 Click Continue.
Select Legacy CCUploader Export File dialog with the exported JSON selected 1 2
  1. 1 Select what you saved in Step 1. The picker takes as many files as you like - so on 1.0.x, select every .CCT file (Ctrl+A in that folder, or Ctrl-click the ones you want).
  2. 2 …and click Open.

A progress bar runs while CC Sync converts your tasks and re-matches their destinations against the server. Everything you selected is handled in one pass: task names stay unique across the whole batch (a second Press 1 arrives as Press 1_1), and a file that can't be read is listed as Skipped in the report while the others carry on. If any task watches a network share, the import pauses to ask for credentials - that's next.

Warning · Import blocked? If CC Sync shows the Admin-Lock message instead of importing, task editing is locked on this machine. Unlock it first (Tasks → Admin Lock), then run the import again.

Step 3 · Network folders ask for credentials

Network-share credentials don't travel with the saved configuration, so CC Sync asks for them once per network folder, and the dialog names the folder it's asking about. What you enter is saved in your operating system's secure storage and reused automatically from then on, including the silent re-mount after a network hiccup.

The import pauses and asks
Input Folder Credentials dialog asking for the network share's username and password, with the import progress bar behind it 1 2 3
  1. 1 Fill in the username and password that have access to this share.
  2. 2 Press Test Connection to check the path and credentials.
  3. 3 When the test passes, press Save - the import continues with the next task.
After a successful test
Input Folder Credentials dialog showing Connection successful after Test Connection 1
  1. 1 Connection successful. - now press Save. A red message instead? Fix the credentials (or the share path) and test again - don't save until the test passes.

If you press Cancel instead, that one task is dropped from the import (the report lists it as Error) - the rest continue normally. Nothing is lost: sort out the credentials and run the import again, or create that task manually.

Concept · Entered once, remembered This is the same mechanism the Task Wizard uses for its Network tab: credentials are stored per folder in the OS keychain, so CC Sync can re-connect the share on its own - no babysitting required.
Tip · A shared folder that came in as local? Older CC Uploader tasks don't always say that their folder lives on the network, so the import can bring one in as a local folder and never ask for credentials. Easy fix: open that task (Step 5), point its input folder at the shared folder, and enter the credentials there - exactly like any other network task.

Step 4 · Read the import report

When the run finishes, Legacy Import Complete sums up the import: the headline says how many tasks came through, and each task that changed on the way gets its notes below. A task that converted 1‑to‑1 isn't listed - it's simply counted in the headline. Anything that couldn't be read at all is counted as Skipped and named with its reason, so a single unreadable file never hides in the total.

Read the notes. Most are purely informational: CC Sync simply behaves differently, and no action is needed. A note only requires action when it says something was not found, asks you to configure something manually, or asks you to confirm a setting - typically a destination that no longer exists on your account, or one the old file didn't describe fully enough. That task still imports; you'll fix it in the next step.

Legacy Import Complete report listing imported tasks with per-task notes 1 2 3
  1. 1 The headline - how many tasks were imported.
  2. 2 Notes appear only for tasks with differences - here Task 2 (Task 1 imported 1‑to‑1, so it isn't listed). Both notes here are informational, so nothing needs fixing: they just say where CC Sync does things its own way.
  3. 3 The house rule: every imported task is paused until you resume it.
Tip · Which notes need action? Notes about delays or postfixes are informational - the task works, CC Sync just does it differently (see What carries over). Notes saying something was not found, needs to be configured manually, or wants a setting confirmed - open that task and finish it before resuming (Step 5).

Step 5 · Review each task

Back in the Task Panel, your imported tasks are waiting - paused (“Task paused on startup.”).

CC Sync Task Panel with two imported tasks paused, each with play, edit and delete controls 1 2 3
  1. 1 Paused status - the task is imported but not watching anything yet.
  2. 2 Double-click a row to open the task's summary for review…
  3. 3 …or press the pencil - same thing.

The Task Summary groups every setting into boxes - the same view the wizard shows before creating a task. Walk them top to bottom against what the old task did: name, folders, file recognition (old wildcards like *_test come through as the equivalent regex .+_test), naming, destination.

Example task 1 after import
Task Summary of the imported local-folder task with grouped setting boxes and an Edit button 1 2
  1. 1 The destination was re-matched by name - here the old task's press and track were found on the account (BB - 9000 / Coated).
  2. 2 Press Edit to walk the whole task through the prefilled wizard - or click any single box to quick-edit just that page.
Example task 2 after import
Task Summary of the imported network-share task 1
  1. 1 The network share came through - it uses the credentials you entered in Step 3.

If the report flagged a task's destination - not found, or a request to configure or confirm it - this is where you fix it: click the Destination box, it opens in quick-edit, and pick the right device, track or project. The same goes for any other box the report pointed at, such as Archive. Save, and the task is complete.

Step 6 · Resume your tasks

Reviewed? Then let them run.

CC Sync Task Panel rows of paused imported tasks with the play button highlighted 1
  1. 1 Press play on a task - it starts watching its folder immediately, and Files Sent starts counting like for any other CC Sync task.

From here on they're ordinary CC Sync tasks - pause, edit or delete them from the row, and see the uploaded data in the CC Dashboard.

Warning · Retire the old CC Uploader Once the imported tasks run in CC Sync, close CC Uploader (or disable its tasks). If both apps watch the same folder, every measurement is processed twice - double uploads, and the two apps' move/delete rules fighting over the same files.

What carries over (and what doesn't)

The quick reference behind the report notes - it holds whichever CC Uploader you came from.

Converted automatically

  • Task names & descriptions - a name that already exists in CC Sync, or that turns up twice in the same import, gets _1, _2, … appended.
  • Input folder - local or network.
  • Output folder → CC Sync's Archive folder, along with the old “delete after upload” choice: keep the original and it becomes a copy, delete it and it becomes a move.
  • File extension - an extension CC Sync doesn't list becomes Other with your string kept; an empty one defaults to .txt.
  • File-name pattern - old wildcards become the equivalent regex, and an exclusion pattern is folded into the same rule.
  • Naming rules - prefix, full rename, and the old “add date to file name” option.
  • Destination - re-matched live against the account you're logged in to.

Not carried over

  • Network share passwords - no CC Uploader version stores them, so you re-enter them once during the import (Step 3).
  • Per-task processing delay - CC Sync has none.
  • Postfix - kept only if the old task also replaced the original name.
  • Running state - every imported task starts paused, by design.

Each of these differences shows up as a note in the import report, so nothing changes silently.

Warning · Coming from CC Uploader 1.0.x? Tasks from the oldest release point at their destination with bare IDs, and those IDs are usually long out of date - CC Sync often can't tell what they refer to on today's account. Such tasks still import, but expect the report to ask you to confirm or re-pick the destination on most of them. Plan on a quick pass through Step 5 before you resume anything.

Next steps

Your tasks are home. From here:

Peter · AI Assistant
Moving from CC Uploader to CC Sync? Ask me about importing your tasks.