Migration

Pike imports your history from the tool you use today, either through a native integration or through CSV templates. Both routes load records in the same dependency order, and neither deletes data in Pike or in the old tool.

​

Two routes

Accounting and CRM stay connected on both routes. Connect your accounting system to bring in customers and invoice history, and your CRM to bring in companies, contacts and deals. See How sync works.

​

Import order

Records reference each other, so Pike loads them in this order:

1. Customers and their contacts.
2. Projects, with phases, budgets and rates.
3. Members, matched by email.
4. Tasks, time entries, expenses and deals.

Import data follows this order on its own. On the CSV route, upload files in this order. A row that references a record Pike cannot find is reported with its line number.

​

Keep syncing during a transition

Native migration integrations have a Keep syncing toggle, off by default. When it is on, new records and time import on the same schedule as every other integration, so one team can work in Pike while the rest finish the month in the old tool. Turn it off at cutover. See How sync works. On the CSV route there is no ongoing sync. Export once, after you freeze changes in the old tool, and re-upload corrected rows: Pike matches each row on its key (customer number, project number or email) and updates the existing record.

​

Cutover

1. Ask everyone to submit and approve their last timesheets in the old tool.
2. Run Sync now (native) or a final time entry upload (CSV).
3. Turn off Keep syncing.
4. Set the old tool to read-only, or reduce its seats and remove edit rights, using the options that tool offers. Each tool’s migration guide on usepike.com lists them.
5. Keep the raw exports in one folder with two owners until the first invoices sent from Pike are paid.

​

What Pike never deletes

An import never deletes Pike data. A record removed in the old tool after import is marked Removed in with the tool’s name and stays in Pike with its history. Disconnecting a migration integration stops syncing and keeps every imported record. Pike does not write to the tool you are leaving.

​

Tools and routes

​

Related

• CSV: Templates, import order and column mapping by source tool.
• How sync works: Schedules, Keep syncing and sync issues.
• Permissions and access: Who runs imports and who sees imported data.
• Migration guides: A week-by-week plan for each source tool.