◆ Google Looker

Migrate data in Looker

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskMigrate the 'Legacy CRM Data' database from our old SQL server to the new Snowflake instance.…+
Migrate the 'Legacy CRM Data' database from our old SQL server to the new Snowflake instance. Map the 'customer_id' from the old system to 'crm_customer_id' in Snowflake and ensure all historical records are preserved.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore I finalize the migration of our 'Website Analytics' data from Google Analytics to our…+
Before I finalize the migration of our 'Website Analytics' data from Google Analytics to our data warehouse, help me identify potential data quality issues. Flag any discrepancies in historical traffic numbers and suggest a robust validation plan to ensure data integrity post-migration.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe marketing team just told me that historical campaign performance data is missing from their…+
The marketing team is reporting missing historical campaign data after the recent migration.
The marketing team just told me that historical campaign performance data is missing from their reports after the recent migration. I'm afraid some data might have been lost or incorrectly mapped during the transfer, which could impact their Q4 planning. What's the most likely point of failure in the migration process, and what's the best immediate action to locate the missing data or confirm its status?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI frequently find myself scrambling to fix data issues or missing fields after a migration is…+
I often discover data inconsistencies or missing fields only after a migration is complete and users start complaining.
I frequently find myself scrambling to fix data issues or missing fields after a migration is supposedly complete, usually when users flag problems. This causes rework and frustrates stakeholders. What habit should I change to proactively catch these issues during the migration process itself, rather than reacting to them afterward?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Google Looker's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.