Migrate to Keito

Use this section to plan, run, verify, and complete a migration from another time-tracking system. Keito currently provides a guided, self-service importer for Harvest during workspace setup.

Keep the source system available until the migration has been reconciled. Do not delete live source data to prepare for an import.

Migration workflow

A controlled migration has four stages:

Stage What you do Exit condition
Plan Choose an owner, scope the data, export a backup, and agree a cutover window Source scope and sign-off owner are documented
Import Connect the source, review preview counts, and run the automated importer Every selected import phase completes
Verify Compare counts, hours, relationships, financial totals, and permissions Business and financial checks are signed off
Cut over Stop new source activity, invite the team, revoke the migration token, and retain a rollback window Keito is the system for all new work

Supported source

Harvest

The Harvest importer can migrate:

  • clients;
  • projects and assignments;
  • tasks;
  • team members and roles when roles are present;
  • time entries;
  • expenses and expense categories;
  • invoices;
  • estimates.

It can also create Keito starter reports for the new workspace. Start with Migrate from Harvest.

If you are moving from another system, contact Keito before changing or deleting the source. The team can help establish what is available and how to reconcile it.

Before starting

Choose one migration owner and one person responsible for financial validation. For a small company these can be the same person, but both responsibilities should be explicit.

Prepare:

  1. administrator access to the source system;
  2. a source export stored securely;
  3. the expected client, project, user, time-entry, expense, invoice, and estimate counts;
  4. an agreed time after which the team will stop entering new source data;
  5. enough source-system access to cover at least one billing and reporting cycle after cutover.

Security rules

  • Treat migration tokens like passwords.
  • Do not include tokens in screenshots, tickets, chat messages, or source control.
  • Use a temporary token when practical.
  • Review imported teammates and permissions before sending invitations.
  • Revoke or rotate the token after validation.
  • Retain exports according to your organisation’s data-retention policy.

Next steps

  1. Migrate from Harvest
  2. Verify imported data
  3. Complete the cutover checklist

For a longer walkthrough with every screen, see the illustrated Harvest to Keito migration guide.