Migrate from Harvest

The Harvest importer runs during Keito workspace setup. It reads the records available to the authenticated Harvest user, creates their dependencies in the correct order, and shows the status of each migration phase.

What you need

• a new Keito workspace;
• a Harvest Account ID;
• a Harvest Personal Access Token;
• a Harvest administrator account with access to the records being migrated;
• the expected source counts for reconciliation.

Create the token in the Developers section of Harvest ID. Harvest’s API authentication documentation has the current token instructions.

1. Configure the Keito workspace

Enter the company identity, currency, timezone, and working-week settings that should apply to new work in Keito.

These are target settings. Review them even if similar values already exist in Harvest.

2. Connect Harvest

On Import from Harvest, enter the Account ID and Personal Access Token, then select Test Connection.

Both fields are masked. Do not expose their values in screenshots or support requests.

If the test fails, confirm:

• the Account ID and token belong to the same Harvest account;
• the token has not been revoked;
• the token owner still has access to the account;
• the Account ID contains digits only;
• neither value has leading or trailing spaces.

3. Review the preview

After a successful connection, Keito shows the number of available records for each supported data type.

Before continuing:

1. compare the preview with your expected source counts;
2. select the Harvest user who represents the current Keito login;
3. confirm archived or inactive records are represented as expected;
4. select the data types you want to migrate.

Stop here if the counts are wrong. Harvest API access follows the token owner’s permissions, so a non-administrator may see only part of the account.

4. Run the migration

Keito runs the import in dependency order:

1. roles and users;
2. clients, tasks, and expense categories;
3. projects and assignments;
4. time entries;
5. expenses, invoices, estimates, and starter reports.

Later records depend on earlier mappings. For example, a time entry needs its user, project, and task before it can be created.

Leave the page open for the clearest progress view. Completed phases persist if the page is closed.

5. Complete setup

When every selected phase finishes, Keito shows a completed state.

Select Complete Setup to enter the workspace. Imported team members are not automatically invited, giving an administrator time to review identities, roles, and permissions.

What happens next

A green completion state confirms that the automated jobs finished; it is not the final business sign-off.

Continue with:

1. Verify imported data
2. Complete the cutover checklist

The full illustrated migration guide includes every import phase and resulting Keito screen.