What moves into Corto

demowho and where

Not a feature. Sign-in decides both of these; until then, this does.

Demo map
Setup

What moves into Corto

Three decisions, each with a name against it. Nothing moves until you decide, and each part switches when its department is released.

Step 2 of 3

Three decisions only you can make

0 of 3
  1. 1

    How much history comes over

    owner · Meera KulkarniCorto's suggestion
    Corto suggests
    Open deals plus twelve months of history
  2. 2

    What gets cleaned before import, and by whom

    owner · Priya DeshmukhCorto's suggestion
    Corto suggests
    The 40 contacts that appear to be duplicates — Priya, with Meera
  3. 3

    The cutover date per module

    owner · Meera KulkarniCorto's suggestion
    Corto suggests
    CRM after the quarter closes; HR record at month end; projects on release
After each switch: one real piece of work in Corto, with the manager beside them2 of 4 done
  • Priya Deshmukh

    her first deal — the Sharma revision · with Deepak Patil

    not yet
  • Suresh Kamble

    his first dispatch update, spoken · with Vinod Shirke

    done 26 Aug
  • Meera Kulkarni

    her first leave approval

    done 26 Aug
  • Ramesh Joshi

    his first chase, drafted and sent by him · with Meera Kulkarni

    not yet
  • Not training. One real job — one deal, one dispatch note, one leave approval — done properly, once. A target can only be read from something people actually use.

0 of 3 decisions made · the rest stay as Corto's suggestion until somebody puts their name to them