Trial entitlement and moving to a paid tenant

What it does

The Customer Insights trial gives you a working environment for 30 days on a restricted entitlement, with an automatically provisioned Dataverse environment behind it. There is no in-place upgrade: a trial never becomes production. You buy the licence, build a fresh production environment, and copy the trial's configuration into it.

Key facts

The trial runs 30 days and can be extended once. The extension only becomes available after day 23, and you take it from within the trial app.
You cannot reset a trial environment and you cannot delete it. If you need a clean start, you wait for expiry and sign up again.
The trial's Dataverse environment is capped at 3 GB of data storage.
You cannot create a trial environment on your own Azure Data Lake Storage account. You can ingest from one, but output stays in the provisioned storage.
Trial, preview and paid tenants have different quota levels. Anything you measure on a trial tells you nothing reliable about paid capacity.
Converting means: buy a Customer Insights licence, create a Production environment in the Power Platform admin center with the Enable Dataverse and Enable Dynamics 365 apps toggles on, then create a new Customer Insights environment with Copy from existing environment pointed at the trial.
The copy carries configuration, not data: data sources (Power Query, Azure Data Lake Storage, Delta tables, Dataverse), unification settings, segments, measures, relationships, exports, enrichments, predictions and role assignments.
Credentials are not copied. Every copied data source needs its connection details re-entered before it will refresh.
Common Data Model and Dataverse data sources are not carried over cleanly and have to be recreated by hand.
Copy environment configuration is a preview feature. Treat it as a head start on rebuilding, not a migration tool.
Trial data is retained in the trial environment until it expires — it does not move with the configuration copy.

When to use / skip

Use a trial for exactly what it is good at: proving the shape of a solution to a sceptical stakeholder, and letting the client's own people touch the unification and segment builders before they commit budget. Thirty days is enough for that and not much else.

Skip it, or run it strictly as a throwaway, if the client has already decided to buy. A trial built by an enthusiastic client team becomes a sunk-cost argument for keeping decisions that were made without any of the production constraints — region, storage, Dataverse binding — in view. On a project with a signed order in hand, go straight to a production environment and use the trial, if at all, as a personal sandbox that nobody presents from.

The trap to watch is the 3 GB Dataverse cap. It is generous enough to make a small proof of concept feel comfortable and nowhere near a realistic volume test, so a trial that runs smoothly tells you nothing about how the real load will behave.

Configuration decisions

Whether to run a trial at all, given it cannot become the production tenant and its configuration only partly transfers.
Who builds in the trial. Configuration built by someone who will not be around for the production rebuild is configuration you will rebuild from screenshots.
Which data sources go into the trial. Common Data Model and Dataverse sources have to be recreated anyway, so favour Power Query and Delta table sources if you want the copy to earn its keep.
Whether to take the extension. It is one-time and only offered after day 23, so it needs deciding before day 30, not on day 29.
When to create the production Dataverse environment. It has to exist, with both toggles on, before the Customer Insights environment can point at it.
Whether to keep the trial alive alongside production for the remaining days, and who is told which one is authoritative.

Gotchas

People assume a trial upgrades in place because most Microsoft trials do. This one does not, and finding out in week four is a bad week.
The extension window is narrow: nothing before day 23, gone at expiry. Miss it and there is no route back to the same environment.
Copied data sources look configured and are not — they sit there without credentials until someone re-enters them, and the first refresh failure is the notification.
Common Data Model and Dataverse sources silently need manual recreation. A copy that reports success can still leave you with sources that were never really carried across.
Trial data stays in the trial. Anyone expecting their sample unification output to appear in production will be disappointed.
Because you cannot delete a trial environment, a half-built one hangs around in the environment picker confusing everybody until it expires.

Consultant notes

Tell the client on day one that the trial is disposable. Put it in writing if the trial is being run by their team rather than yours, because the expectation that it converts is the default assumption.
Demo the Copy from existing environment checkbox during the production build so the client sees what does and does not come across. It manages the expectation better than describing it.
Keep a written record of trial configuration — unification match rules especially — rather than relying on the copy. Preview features are not a backup strategy.
Before the production build, confirm the Dataverse environment exists with Dataverse and Dynamics 365 apps enabled. It is the most common reason the new environment wizard stalls.
Diary the day-23 extension window if the trial is on the critical path. Nobody remembers it, and there is no second chance.

Worth another look when Copy environment configuration leaves preview, or if Microsoft ever adds a direct trial-to-production upgrade.