BC Migration from Studio to ES [WIP]
Draft Buildcard Migration
Current system
If a user is Studio Pro → converted to ES user → looses access to Studio Pro
•
If tries to access → redirected to ES
•
Exceptions - Now/Home?
•
BC stays in Studio and no transfer of BC happens
•
Invited user (non ES) continues to view the current BC of the respective account
•
Invitation flow to be tested on prod in conjugation with the invitation flow of Studio
•
Why
Customer during the acquisition funnel can be proposed for ES offering
•
Draft BC can be created on Studio by Productologist which are essentially for ES offering
•
Estimation is required to be reviewed by the customer and the business team for ES credits
•
The objective is to transfer the BC in all states available on Studio Pro for a
customer to Enterprise Surface.
Objective
The objective is to transfer the BC in all states available on Studio Pro for a customer to Enterprise
Surface.
These BCs are after migration should be available on the respective ES account.
•
The currency should be converted to ES credits of the given BCs
•
The BC type to be updated as Enterprise Surface
•
Upsync tier details of the BCs to Studio
•
Limitation
BC is BNPL cannot be migration
•
BCs can be migrated only in new account owner → If new account is being created and if the
•
user is owner of any of the BC within Studio → New account cannot be created
Manual Approach
1. If the CIO already has Studio account and is the owner of the BC → All BC from the account
should be visible inside ES
2. If the CIO is invited to a BC → these BC can be moved to the CIO ES account. This would be
case by case
3. Create a default space when a new account is set up and migration is required
4. All Draft BC →
a. Currency should be in credits
5. For completed and running BCs →
a. On ES show original BC meta data that includes currency as well and show in k format
of the currency value ($250K)
b. Show static migration directly to Studio Home from ES (opens in new tab)
c. All payments and subscription runs normal as per studio
d. No addition to this BC to respective ES credits
e. All CR and SCR will be maintained directly from Home
Automated Process
Approach
Pre-migration
Enterprise surface creates a user ES and asks Studio to mark as Enterprise Surface user
•
[already built]
Check if BC is completed or draft
•
Show necessary details of the BC
•
Ask for account in which BC are to be migrated
•
Take confirmation before migration
•
Start the migration process
•
During Migration
1. Invoices correction? → See point 9
2. Studio One
a. For completed BCs →Any future Studio one subscription renewal would be stopped and
fresh Subscription would be started on ES of E1 for one year and credits to be deducted
after the migration is completed
i. What about the upfront payment (customer has already paid entire 1,2,3 year→
ii.
b. For running BCs →
c. Draft BC →
3. Delivery upgrade → new squad handling → Delivery
a. For completed BC → no change in the squad
b. For running BC → no change in squad till BC is completed
4. PDF regeneration? → BC PDF remains the same, until the BC is updated (we need to see if
currency is updated, does the Studio updates the BC PDF as well, if it does not then do not
change the BC PDF and wait for the next version of the PDF)
5. Downsyc BC details to other systems → Check 360 system
6. Open BC change request
a. Completed BC → The change request should be shown to the user on ES as per the
change request flow.
i. Draft CR → show as it is in credits
ii. Pending approval CR → Show approval pending delivery in credits and deduct the
credits
1. If the credit is not available in the account → decline the delivery approval or
change the status of internal approval of the change request
b. Running →
7. Scope CR Feature → Scope of the feature is changed
8. Consumption on ES post migration
a. Draft → start consuming the credits
b. Completed → Do no consume any credits but show the credits in the UI
i. Scope CR → Credit consumption as per 6
ii. CR → Credit consumption as per 6
c. Running → Do no consume any credits but show the credits in the UI
9. MSA management → Where is the visibility of MSA for customers
10. Current invoices on Home → Do not show to the customer and previous paid invoices can be
shared with the customer on demand
Post Migration
A new space in the given account is created. Name of the space - "My space" and these BCs
•
should be available on the respective ES account.
Studio in turn to provide all the meta-data of the BCs so that it can be consumed by
•
Enterprise.
Open Questions
1. What happens when a member is being invited and the member owns a BC on Studio
a. Guardrails around inviting the member from Studio and ensure that if user has
ownership of BC on Studio → should not be allowed to added as a member
2. Invited members on the BCs for previous BCs?
3. Roll back of migration
Approach
A tool where list of BCs IDs can be added and an ES account email address is provided where
•
the BCs are to be moved.
For validation
•
Names of the BC and the current owner to be shown
•
Check if BCs are in draft
•
Validity of the existence of ES account is checked
•
Validation failure
•
If BC id is not found → show not found
•
If BC is NOT in draft → Can't be migrated
•
If ES account not found → No account found
•
Upon verification, admin user should be allowed to migrate the BC in the given ES account.
•
Upon initiation
Update the currency of the BC to ES credits
•
Change the BC type to Studio Enterprise
•
Update the owner of the BCs
•
A new space in the given account is created. Name of the space - "My space"
•
Owner of the space is the account owner
•
All the validated BC to be shown in the new space with lead as the account owner
•
•
Flow
https://whiteboard.builder.ai/board/043d1800fac4e3a249f554d4b104b2d83b2f7d79deec35226ed
28e0714d8e897
Paid and running Buildcard Migration
[WIP]
