Steps for Tenant Cloning from the Customer’s Side

1. Ticket Submission: The customer must log a ticket via SNOW requesting a test tenant refresh/cloning.

2. Information Required from the Customer: The customer must provide their confirmation on the following details for the test cloning/refresh process:

The following data from the production (SOURCE) environment will be copied to clone the test(TARGET) environment:

• Transactional data (Invoice and PO data)
• Master data (User data, user group data, supplier data, EXT table data, lookup lists, etc.)
• Invoice/Purchase process–related configuration

To scope the request accurately, Basware will need clarification on the following:

• Whether user notifications should be disabled in the test environment after the cloning.
• Whether the customer wants to copy invoice images/PDFs from production (this incurs additional charges).
• Preferred cloning window — weekday or weekend (cloning during weekends will incur extra charges).

Note: During the refresh, the Source tenant must be taken offline for approximately 30 minutes to 1 hour, depending on the database size.

Post-Information Submission (Basware Actions)

Once Basware receives the required information, we will contact the Basware SaaS team to obtain the cloning estimate.
(This request is only for estimation purposes and is not the actual cloning execution.)

The SaaS team will provide:

• Database size
• Size of invoice images (only if the customer opts for copying images during cloning)

Billing Rules

• If the total cloning data size exceeds 25 GB, the cloning request becomes billable.
• In this case, Basware will inform the customer of the estimated cost, and cloning will proceed only after customer approval.
• If the data size is below 25 GB, the cloning is free of charge.

After the cost confirmation from customer, Basware team will perform the tenant cloning and hand over the refreshed test tenant to the customer and ask them to verify before closing the ticket.