AGENT ORIENTATION

The safe way for an AI agent to prepare a Profitdrive migration.

Share this page with an AI assistant before it touches a source spreadsheet. It starts from your existing tenant, selects the relevant migration scope, and sets out the import order and checks that turn accounting history into operational control and a forward-looking plan.

START HERE

Read https://www.profitdrive.app/en/agent/migration/guide and help me migrate my company to Profitdrive. Work through the numbered plan one substep at a time. First ask whether I already have a Profitdrive tenant. If I do, select the Core, Structured or Advanced migration scope before asking about any Settings; then use current Settings as the baseline rather than repeat onboarding. Show proposed changes before writing; once I explicitly approve an action, carry it out if you have access, then verify and report.

CHOOSE THE MIGRATION SCOPE

Start with the tenant you have, then add only the structure you need.

These are migration scopes, not labels for company size. An agent should first establish whether your tenant already exists, then select the scope. If it does, current Settings remain the baseline; after scope selection, it asks only about migration-relevant gaps or planned changes rather than repeating new-tenant set-up questions.

Core

Firm working calendar, employer on-cost, margin targets, people, historical won work, Deal Models, pipeline, SG&A, and actuals or budget.

Structured

Core, plus teams, locations, location-specific employer on-cost, and an optional grade catalogue or grade-costing approach.

Advanced

Structured, plus non-reporting cost currencies, exchange rates, and the later decision to use Xero for actuals.

Written for an agent. Clear enough for the person who remains responsible.

An agent should prepare, check and explain. The user owns the source data, approves every proposed correction and decides when an import or connection may proceed.

RECOMMENDED MIGRATION SEQUENCE

Six headline steps. Short substeps. One clear route through.

Your agent should work through one numbered substep at a time. Pause whenever you need to and resume by referring to the last item, for example “resume at 02.2”.

  1. 00

    Settings

    00.1 Confirm whether the tenant exists. 00.2 Choose the scope. 00.3 Review only the tenant-wide working calendar, cost settings and margin targets that are relevant to the migration.

  2. 01

    People

    01.1 Prepare the source and current template. 01.2 Review corrections. 01.3 Approve and import People before dependent records.

  3. 02

    Projects

    02.1 Import each historic opportunity. 02.2 Review its Deal Model. 02.3 Only then move that selected opportunity to Won.

  4. 03

    Pipeline

    03.1 Add live opportunities. 03.2 Add draft changes manually. 03.3 Review each action; no unsupported bulk route is invented.

  5. 04

    SG&A

    04.1 Classify monthly planned cost lines. 04.2 Import with the current template. 04.3 Review category mappings and results.

  6. 05

    Financials

    05.1 Choose actuals import or Xero. 05.2 Load budget. 05.3 Reconcile the resulting financial inputs.

YOUR DATA, YOUR DECISION

An agent can prepare and explain. It should not decide for you.

A useful migration assistant preserves your original file, identifies gaps and proposes only traceable changes before an upload. When you explicitly approve an action, it can carry it out if it has access, then verify and report what happened. You can also do every step yourself.