Migration guide
Export Scoro list views and the Detailed report as CSV and upload them to Pike templates, with five to six weeks from first export to cutover.
Available now
Scoro exports each list view as CSV or XLS for anyone whose permission set has the Export data right, so you export once per entity and upload each file to the matching Pike template.
Scoro bill rates come from the product linked to each activity type and from price lists. Check whether your project export includes the hourly rate, and add `hourlyRate` by hand where it does not.
Available now
Scoro integrates with Xero, QuickBooks and HubSpot. Connect your ledger and CRM to Pike before you load projects, so customers and invoice history come from the ledger.
Disconnect the Scoro side of each accounting and HubSpot integration at cutover, so invoices go to the ledger from Pike only.
Entity map
Column one uses Scoro’s own labels. Pike matches people on the email of each Scoro user and links records on project number and customer number.
Pike: Customers
Carries over: Each company contact marked as client.
You set in Pike: Customer number and VAT ID, unless your Scoro export includes them.
Template columns: customerName, customerNumber, taxVatId, mainCurrency
Pike: Customer contacts
Carries over: Each person contact linked to a client company.
You set in Pike: Nothing.
Template columns: customerNumber, name, email, title, phone
Pike: Projects
Carries over: Project number, name, client, status (pending, in progress, future, completed, cancelled), project manager, project type (regular, retainer, internal), revenue model, budget type (quote or simple).
You set in Pike: Retainer periods for retainer projects, and Capped Time and Materials on projects Scoro marks as capped.
Template columns: projectNumber, title, customerNumber, status, billingType, budgetAmount, budgetHours, hourlyRate, startDate, endDate, leadEmail
Pike: Phases
Carries over: Phase name, type (phase or milestone), start and end dates.
You set in Pike: Pike’s template has no milestone type. Load a milestone as a phase with the same start and end date.
Template columns: projectNumber, phase, startDate, endDate
Pike: Tasks
Carries over: Title, project, phase, assignees, planned duration.
You set in Pike: One assignee per row. Scoro tasks can have several, so pick the owner before upload.
Template columns: title, projectNumber, description, status, phase, assigneeEmail, startDate, dueDate, billableStatus
Pike: Time entries
Carries over: Date, duration, billable duration, billable type (billable, non_billable, custom), submitted, confirmed, locked and billed flags.
You set in Pike: Nothing.
Template columns: date, hours, email, projectNumber, taskTitle, note, billableStatus, approvalStatus, invoiced
Pike: Project hourly rate
Carries over: The product linked to each activity type sets the price of an hour of that activity.
You set in Pike: One `hourlyRate` per project in the file. If your team tracks by activity type, use the activity name as the task title.
Template columns: hourlyRate
Pike: Project hourly rate
Carries over: Role prices.
You set in Pike: Work out the rate each project bills at and enter it as `hourlyRate`.
Template columns: hourlyRate
Pike: Members
Carries over: Email and name. Labor cost (hour cost per user per date) is a separate setting.
You set in Pike: Cost profile from the current Scoro hour cost, plus team and position.
Template columns: email, displayName, team, position
Pike: Deals
Carries over: Quotes with an estimated closing date.
You set in Pike: Check whether your quote export includes value, status and probability, and fill in what it does not.
Template columns: title, customerNumber, status, value, probability, closeDate
Pike: Invoice history from your accounting system
Carries over: Paid or unpaid state in Scoro.
You set in Pike: No CSV import. Pike reads invoice history from the connected ledger, and new invoices go out from Pike from cutover.
Scoro prices an hour through the product linked to each activity type, and price lists set role prices. Pike’s project template takes one `hourlyRate`, so work out the rate each project bills at before upload.
Labor cost in Scoro is an hour cost per user per date. Set each member’s Pike cost profile from the current hour cost. For projects budgeted from a quote, enter the quote total as `budgetAmount`.
Scoro’s revenue model (fixed_fee, tm_capped or tm_not_capped in the Scoro API) maps to `billingType`: fixed fee to `fixedFee`, uncapped time and materials to `timeAndMaterials`, and capped time and materials to `timeAndMaterials` with the cap as `budgetAmount`. Internal projects import as `nonBillable`.
The plan
The same steps as the main migration guide, with this tool's screens and settings.
Week 1
Migration owner, finance
Week 1 · Migration owner, finance
On CSV the first export is your migration data. Note its date: you export the time after it again at cutover.
Done when: Raw Scoro exports in one folder with the export date written down, and a cutover Friday on the calendar.
Week 1 to 2
Operations lead
Week 1 to 2 · Operations lead
Clean the exported CSV files. Nobody edits Scoro after export day.
Done when: Every open project has a project number, billing type, budget and rate. Every user has the email they will sign in with.
Week 2
Workspace admin
Week 2 · Workspace admin
Connect the ledger first, so the customer numbers in your Scoro files match the customers Pike imports from accounting.
Done when: Admins and leads are in Pike. Finance sees the same customer list as the ledger.
Week 2 to 3
Workspace admin
Week 2 to 3 · Workspace admin
Upload customers, contacts, projects, phases, members, tasks, time entries, then deals. Pike reports a missing reference with its line number.
Done when: Customer, project, user and last-month hour counts match Scoro.
Week 3 to 5
Delivery lead, finance
Week 3 to 5 · Delivery lead, finance
On CSV there is no ongoing sync. The pilot team logs time in Pike only, and everyone else keeps logging in Scoro until cutover.
Done when: One invoice sent from Pike. No pilot team time in Scoro after the pilot start date.
Week 5 to 6
Migration owner
Week 5 to 6 · Migration owner
Close Scoro on Friday evening and upload the time logged since your first export.
Done when: Time admin shows every active member by Monday afternoon. Scoro shows no time after Friday.
Week 6 to 9
Finance
Week 6 to 9 · Finance
Done when finance closes a month without opening Scoro.
Done when: Month closed in Pike. Final Scoro export saved with two owners. Scoro subscription ended.
Rebuild
Questions
The Scoro project list shows only active statuses by default. Add completed and cancelled statuses to the filter before you export, or past time entries reference projects Pike cannot find.
Scoro marks each time entry as submitted, confirmed, locked and billed. Map confirmed entries to `approved` and billed entries to `invoiced` = `yes`, and Pike keeps them off new invoices. Time locking is available on Scoro Enterprise and legacy Pro and Ultimate plans.
Upload them as projects, then turn on the retainer in Pike and set the billing period, hours and fee per period. Unused budget in Pike does not roll over between periods.
Open quotes with an estimated closing date become Pike deals, with the closing date as `closeDate`. Quotes used as project budgets set `budgetAmount` on the project.
Scoro records a duration and a separate billable duration on each time entry. Map duration to `hours`, and review entries marked custom by hand and compare their billable duration with the logged duration.
Scoro’s terms give 30 days after termination to download your data, and 5 days to report a problem with an export. Run your final exports before you give notice.
ISO 27001
GDPR
SOC 2 Type IIBuilt to keep sensitive client data secure and private.
