Akhir Pekan Cutover

🌐 Juga tersedia dalam 19 bahasa

English · Español · 日本語 · Português (Brasil) · Français · Deutsch · Italiano · 한국어 · 简体中文 · Português (Portugal) · 繁體中文 · Türkçe · Polski · Tiếng Việt · ไทย · Українська · Español (México) · Français (Canada) · Deutsch (Schweiz)

Gambar dibuat dengan AI

Diterjemahkan dengan AI. Belum ditinjau oleh komunitas. Baca dalam bahasa Inggris Bagian ini telah berubah dalam bahasa Inggris dan belum diterjemahkan ulang. (54)

Modul 4 dari 5 dalam bab Migrasi dan Sinkronisasi, bab 10 kursus Data Architect. Setiap modul dapat dibaca secara mandiri. Previous: Automation During the Load · Next: Getting Data Out: Keeping Another System in Step ⟲

Pertanyaan yang dijawab modul ini: Bagaimana Anda beralih, dan membuktikan bahwa migrasinya berhasil?

Jumat malam. Pengguna sudah keluar, tim migrasi sudah online, dan seseorang berkata, “Kita sudah menguji ini tiga kali. Ayo jalan.” Oke. Apa persisnya yang akan kita lakukan? Kapan sistem lama berhenti berubah? Kapan ekstrak terakhirnya? Siapa yang mematikan otomasi, siapa yang memulai setiap pemuatan? Bagaimana jika pada tengah malam kita terlambat dua jam, atau 3 persen akun gagal? Siapa yang memutuskan apakah kita lanjut? Bagaimana kita membuktikan datanya benar, dan kapan pengguna bisa kembali? Dan jika semuanya buruk: bagaimana kita keluar? Cutover bukan “jalankan migrasinya.” Ia transisi terkendali dari satu status yang diketahui ke status lain.

Start With the Picture

Here’s our landscape one more time. This is the weekend that amber arrow runs, and then disappears. ⟲

Klik untuk memperbesar

The weekend this arrow runs. On Monday morning, it’s gone. ⟲

But more changes that weekend than one arrow. The partners’ manifests stop landing in RouteDesk and start arriving through the integration layer. RouteDesk’s own outbound feeds, Keystone’s nightly status file and Redrock’s webhook, have to come from Salesforce instead. Coordinators route Monday’s deliveries in Field Service, not RouteDesk. And on Monday morning, 330 trucks leave the distribution centers on routes from the new system. Everything in this module is about getting to that Monday safely, and knowing what we’d do if we couldn’t. ⟲

Produksi Seharusnya Membosankan

Saya ingin cutover produksi terasa hampir mengecewakan. Kita sudah menjalankan prosesnya, mengukur waktunya, melihat kegagalannya, menguji bypass-nya, merekonsiliasi hasilnya, dan berlatih memulihkan operasi normal. Produksi adalah buku panduan yang sama dengan data baru. Jika kita baru menciptakan migrasinya pada akhir pekan cutover, kita sudah dalam masalah.

That takes a dress rehearsal, not “we loaded accounts in the sandbox.” Beginning to end: a final-style extract, transformations, quality checks, the load sequence, automation and integration controls, reconciliation, deferred processing, the return to normal mode, all timed, at production or representative scale, in a Full sandbox. Record how long each step took, what failed, what needed manual help, what confused people, where we waited, what surprised us. Then improve the runbook. The first rehearsal teaches you how the migration works; the next one should prove you learned. And because module 2 brought the keys back, a rehearsal doesn’t have to start from nothing every time: fix one transformation, reload just the rows it touched, and run the reconciliation again. For RouteDesk, that means the whole weekend in a Full sandbox: the extract, the preparation data store, the waves of module 1, the bypass of module 3, the switch of the partners’ feeds, and the reconciliation, with a stopwatch running. ⟲

Runbook Adalah Arsitektur yang Bisa Dijalankan

Bukan “Sabtu pagi: migrasikan data.” Melainkan lebih seperti:

Langkah	Tindakan	Pemilik	Perkiraan durasi	Bukti / kriteria keluar
1	Confirm RouteDesk is read-only after Saturday’s last truck	Operations lead	10 min	Written confirmation; time of the last change recorded
2	Final RouteDesk extract into the preparation data store	Data team	45 min	Counts and control totals captured
3	Confirm the bypass on the migration user	Salesforce team	10 min	A test record saves with no status events sent
4	Incremental load: Saturday’s changes, upsert by the partner key	Migration team	30 min	Results and new IDs back in the preparation data store
5	Reconcile against the expected numbers	Data team and operations	30 min	Counts, totals and aggregate reports approved
6	Switch the partners’ manifests and status feeds to the integration layer	Integration team	30 min	One test manifest upserted and one status sent, per partner
…	…	…	…	…
14	Remove the bypass from the migration user	Salesforce team	10 min	Permission set unassigned, and checked

Now we know what happens, who does it, how long we expect, and what proves each step is complete. That’s much stronger than a checklist that says “Load Work Orders.” Notice step 14. Module 3’s bypass is a permission to skip business rules, so taking it away is a runbook step with an owner, not something we hope someone remembers. ⟲

H−7, H−1, Hari H

I call go-live Day 0: usually a Sunday or another off-hours day. Steve Trucking delivers six days a week, so Day 0 is the Sunday with no trucks on the road. Day +1 is after it; Day −1 and Day −7 are before it. And on any large load, I ask: do I have to wait until Day 0 to load all the data? If the load takes hours and the source keeps changing, I’m going to need an incremental anyway. So: ⟲

• Day −7: the initial load. Load the bulk of the data a week early, kept invisible by sharing, so users and reports don’t see it. Smoke-test users (a system administrator) validate it in place. Ask the business what would be hurt by loading early; if the answer is “it would break my reports,” load it hidden. It’s much simpler to open up the sharing on Day 0 than to spend five hours loading a million records and all their children inside the window. ⟲
• H−1: pemuatan penyegaran. Bawa apa yang berubah sejak H−7, dan lindungi garis startnya: apakah pengguna masih mengubah sumbernya, apakah integrasi masih menulis, apakah job terjadwal masih berjalan? Bekukan sumbernya, jadikan hanya-baca, atau tetapkan persis bagaimana perubahan setelah ekstrak akan ditangkap.
• Hari H: pemuatan inkremental. Muat apa yang berubah sejak H−1 (kadang satu inkremental di awal jendela dan satu terakhir di akhir), rekonsiliasi, putuskan go atau no-go, buka berbaginya, pulihkan operasi normal.

For RouteDesk, Day −7 is the Sunday before: the 190,000 delivered Work Orders go in, hidden by sharing, and smoke-test users check them all week. History barely changes, so most of the load is done before the weekend starts. Day −1 is Saturday night, once the last truck is back: RouteDesk goes read-only, and the refresh brings the week’s changes. Day 0 is Sunday: a small incremental, then the gates. ⟲

Klik untuk memperbesar

Day −7: most of the data, a week early, where nobody can see it yet. ⟲

Klik untuk memperbesar

Day −1: the week’s changes, and the source stops moving. ⟲

Klik untuk memperbesar

Day 0: a small incremental, then the gates. ⟲

Klik untuk memperbesar

Day +1: the first truck leaves, and the rollback clock runs out. ⟲

This isn’t an unusual way to cut over; it’s the common one, under other names. Salesforce’s own guidance for moving a B2C Commerce site says to migrate as much data as you can “as close as possible prior to the actual cut-over. Ideally, only the delta from the previous day should be required to copy during the cut-over to minimize the down time” (B2C Commerce Realm Split FAQ (terbuka di tab baru), Salesforce Help). Microsoft’s guidance for its own platform is a full migration “about a month before go-live, followed by weekly delta loads,” with the final delta “after freezing both source and target systems” (Data migration planning for go-live (terbuka di tab baru), Microsoft Learn). And AWS’s database migration service builds the same idea in: a full load while it captures changes, then “shut down your applications, let the remaining changes flow through to the target” (Components of AWS DMS (terbuka di tab baru), AWS; all three checked 2026-10-27). The timing changes with the volume: a month or a week ahead, weekly or daily deltas. The Salesforce twist is the one I add: load early hidden by sharing, so the data is in place and checked, and nobody sees it until Day 0. ⟲

Test knowledge. For a large migration with a short cutover window, load most of the data days early, hidden from users by sharing, then load only what changed (a refresh before the window, an incremental inside it). Freeze or capture changes in the source from the extract onward, and validate with test users before opening access. ⟲

For the cutover, the point is the gates around those loads. By Day −7 I don’t want to be designing the migration anymore: mappings, transformations, the load sequence, automation decisions, migration identities, reconciliation reports, the runbook, rollback criteria and known exceptions are stable, because the real loads have started. Things can still change, but every late change reduces rehearsal. At some point you stop improving the migration and start protecting the cutover. And know when the source stopped moving, or know exactly how you’ll capture what changed after your extract. ⟲

That second half is the watermark: the point through which each extract was current, so the next load knows what changed since. For RouteDesk, the watermark is the moment of each extract: everything RouteDesk changed after Sunday’s Day −7 extract is in Saturday’s refresh. That only works if RouteDesk records when a delivery last changed, so check that it does, and that every DC’s screens update it. If it doesn’t, compare snapshots: extract again and find the differences by key. Slower, but it’s a watermark you can trust. Without one, delta processing is guesswork. ⟲

Lalu Hari H adalah eksekusi. Ikuti runbook-nya, catat waktu sebenarnya, ID job, jumlah, error, dan keputusan. Jika langkah 17 gagal, jangan lompat ke langkah 24 karena seseorang mengira itu menghemat waktu: pahami dependensinya, pakai prosedur pemulihan, perbarui statusnya. Tim harus selalu bisa mengatakan di mana kita sekarang, apa yang selesai, apa yang gagal, apa berikutnya, dan apakah kita masih di dalam jendela waktu.

Kunci Pengguna di Luar Ketika Anda Butuh Kendali

Tak seorang pun suka downtime. Tetapi berpura-pura sistemnya tersedia sementara kita mengganti fondasinya bisa lebih buruk, dan “kami ingin nol downtime” tidak boleh diam-diam menjadi “kami sama sekali tidak tahu versi data mana yang otoritatif.” Kadang strategi paling bersih adalah mengunci pengguna di luar, melakukan cutover, membuktikan hasilnya, dan membawa mereka kembali. Bagaimana caranya?

• Cara keras: bekukan pengguna, ubah jam login mereka, atau batasi rentang IP. Jangan nonaktifkan mereka: itu merusak kepemilikan dan semua yang terkait dengannya.
• Cara lunak: login flow yang membiarkan orang masuk lalu menaruh mereka di ruang tunggu: “sistem sedang dalam pemeliharaan; silakan kembali nanti.” Lebih ramah daripada error yang membuat pengguna mengira akunnya rusak. Jangan pernah memasang login flow itu pada administrator sistem; jika ia rusak, tak ada yang bisa masuk.
• Selalu sisakan pintu belakang: sekelompok administrator sistem (dan pengguna smoke test Anda) yang tetap bisa masuk.
• Sesi tetap bertahan. Mengunci pengguna di luar tidak mengakhiri sesi yang sudah terbuka, jadi rencanakan cara mengeluarkan orang yang masih bekerja: pemberitahuan, tenggat waktu, atau, dengan pekerjaan kustom, cara untuk me-log-out mereka.

At Steve Trucking it’s Sunday, so the people to plan for are the care agents answering phones, the coordinators getting ready for Monday, and the 300 Retail Partner users who might log in to the portal to check a claim. Login flows are assigned by profile (Custom Login Flows (terbuka di tab baru), Salesforce Help, checked 2026-10-27), so the partners’ profile can get the waiting room (“your deliveries are moving to a new system; back Monday at 6 a.m.”) while the smoke-test users and administrators come and go. ⟲

Jangan mengarangnya seminggu sebelumnya. Putuskan apa yang akan dialami pengguna, dan beri tahu mereka.

Test knowledge. To keep users out during a cutover, freeze their accounts, restrict login hours or IP ranges, or use a login flow (assigned by profile) as a waiting room. Don’t deactivate users: it breaks ownership and what’s attached to it. Keep administrators and test users able to log in. ⟲

Go/No-Go, dan Jam Rollback

Pukul 2.00 dini hari, dua belas jam berjalan, bukan saatnya mengarang kriteria go/no-go. Tetapkan sebelum cutover: objek kritis sudah direkonsiliasi, tingkat kegagalan di bawah ambang yang disetujui, tidak ada cacat data kritis yang belum terselesaikan, hubungan wajib sudah divalidasi, integrasi kritis sudah diverifikasi, otomasi sudah dipulihkan dan diuji, kinerja dapat diterima, validasi bisnis sudah dilakukan, waktu yang tersisa cukup untuk langkah-langkah hilir. Jika tidak, “go” menjadi “kita sudah sejauh ini.” Itu bukan arsitektur. Itu bias sunk cost.

“We have a rollback plan.” Good. Until when? We migrate, open Salesforce, and for six hours users create cases, update accounts, enter opportunities, change contact details, while integrations send data elsewhere. Can we restore Friday night? Not without losing legitimate work. Rollback gets harder the longer the new system runs, so define the rollback point: before it, we return to the previous state with the tested procedure; after it, recovery needs a different strategy. Rollback has a clock, and the runbook should show it. For Steve Trucking the clock is easy to read: until Monday’s first truck leaves on a Field Service route, we can still send the coordinators back to RouteDesk, which is why it stays read-only and untouched until then. After that, every delivery made, photo taken and status sent lives only in Salesforce, and going back would lose real work. From that moment, recovery means fixing forward. ⟲

Rollback juga bukan sekadar menghapus apa yang Anda muat. Otomasi mungkin sudah membuat anak, integrasi mungkin sudah mengirim rekaman ke tempat lain, pengguna mungkin sudah mengubah rekaman yang dimigrasikan, file mungkin sudah dilampirkan, event sudah diterbitkan, rekaman yang ada sudah diperbarui. Efek yang tersebar itulah sebabnya kontrol otomasi dan integrasi di modul 3 adalah arsitektur cutover.

And what makes you roll back? In my experience it’s rarely the loader. It’s unknown data: you find out something key was missed, or a data feed was running that nobody accounted for. The best rollback plan is not needing it: know all of your key data, and every feed that touches it, before cutover. RouteDesk has two that are easy to forget, because they go out, not in: the nightly status file Keystone picks up, and the webhook that tells Redrock what happened. Retire RouteDesk without moving them, and on Monday night Keystone hears nothing. Nobody loaded the wrong data; a feed just stopped. ⟲

Empat Cara Saya Membuktikan Data

Setelah pemuatan saya tidak bertanya “apakah API bilang sukses?” Saya ingin empat jenis bukti, dan saya memakai keempatnya: jumlah, total, pemeriksaan acak, dan laporan agregat.

Jumlah. Berapa rekaman yang seharusnya ada, dan berapa yang ada? Akun sumber terpilih: 500.000. Duplikat dikonsolidasikan: 20.000. Dikecualikan menurut kebijakan yang disetujui: 5.000. Diharapkan: 475.000. Target: 475.000. Bagus, tetapi jumlah saja bukan bukti; Anda bisa punya jumlah rekaman yang benar dan data yang salah.

Total. Di mana angka penting, bandingkan total kontrol: nilai faktur, nilai pesanan, saldo terbuka, kuantitas. Kedua sistem punya 100.000 faktur, tetapi sistem lama bertotal $412.800.000 dan Salesforce $398.100.000. Berhenti. Total memperlihatkan apa yang terlewat oleh jumlah.

Spot checks. Look at real records, not just easy ones: a simple record and a complex one, a large customer and a small one, one with many children, one that was transformed, one involved in dedupe, one with unusual history. Trace each from source to target: fields, relationships, ownership, history, External IDs. Averages hide serious individual failures. ⟲

Laporan agregat. Bandingkan bentuknya: akun per negara bagian, pesanan per tahun, kasus per status, pelanggan per segmen, pendapatan per bulan. Jika sumbernya berkata 82.000 pelanggan di Arizona dan Salesforce berkata 8.200, kita punya petunjuk: kode negara bagian yang tidak terpetakan, satu tahun yang dikecualikan, status yang salah diterjemahkan, file yang terlewat. Jumlah barisnya bisa tampak baik sementara distribusinya yang bercerita.

For RouteDesk, each proof has its check, and each catches something the others miss. ⟲

Klik untuk memperbesar

Each proof catches what the others miss. Use all four. ⟲

The aggregate report is the one I’d watch first. Remember module 1’s status codes: nine DCs, nine spellings. If DC 7’s deliveries by week come out 40 percent short against RouteDesk’s, the count for the whole load might still look close, but one DC’s DONE/INST didn’t map. ⟲

Test knowledge. Prove a migration with more than “no errors”: record counts against expected numbers set before the load, control totals on amounts that matter, spot checks of real records traced end to end, and aggregate reports that compare the shape of the data. Business owners validate it too. ⟲

Dua aturan menyertainya. Pertama, tetapkan angka yang diharapkan sebelum pemuatan (modul 1): jumlah sumber, pengecualian yang disetujui, duplikat yang dikonsolidasikan, rekaman yang dikarantina, target yang diharapkan. Lalu bandingkan dan jelaskan selisihnya. Angka harapan yang dikarang setelah melihat hasilnya bukan rekonsiliasi; itu rasionalisasi. Kedua, nol error tetap bisa salah. Petakan Billing State ke Shipping State dan setiap baris dimuat tanpa error API: eksekusi teknis sempurna, arsitektur salah. Itulah sebabnya rekonsiliasi bisnis penting, bukan hanya log teknis.

Pemilik Bisnis Juga Memvalidasi

Tim teknis bisa membuktikan jumlah, kunci, hubungan, dan keberhasilan pemuatan. Pengguna bisnis mengenali apa yang tidak kita kenali: “ini bukan pelanggan aktif kami,” “status itu tidak dipakai sejak 2022,” “akun-akun ini masuk wilayah yang salah,” “pelanggan ini seharusnya punya tiga kontrak aktif.” Jadi validasi bisnis adalah langkah go-live yang eksplisit, dengan orang bernama, laporan bernama, rekaman bernama, dan persetujuan bernama, bukan “lihat-lihat saja kalau ada waktu.”

Authority Moves on Day 0

Why not move everything on Day 0? The Number of Zeros. If the full migration takes 18 hours and the business tolerates 4 hours of downtime, we have a problem, and moving data earlier solves it. History goes in before cutover while the legacy system stays authoritative; the window only has to handle what changed, what couldn’t be preloaded, final relationships, validation and reconciliation. Instead of moving eight years of history during the outage, we’re closing a gap. ⟲

But preloaded data needs protection. If production data lands on Day −7, can users see it, edit it, can automation react, can integrations publish it, can agents act on it? The answer should be: not yet. So we keep it hidden by sharing, owned and controlled, with automation and integrations held back (module 3). A preload isn’t “put the records in early.” It’s put them in early without accidentally making the new system authoritative early. ⟲

Before cutover, the legacy system is authoritative and Salesforce holds a staged, increasingly current copy. During cutover we close the gap. At the agreed moment, authority moves, and afterward Salesforce is authoritative. For Steve Trucking that moment is Day 0: from then on, a delivery’s truth lives in Salesforce, and RouteDesk is a read-only record of the past. That’s where chapters 6, 9 and 10 meet: identity, authority, movement and cutover aren’t separate problems; they’re views of the same data lifecycle. ⟲

So don’t let two systems both think they’re master. If the legacy system stays writable after cutover, a coordinator changes a delivery window in Salesforce, another changes it in the legacy system, and both systems think they own it. Last write wins? Salesforce wins? Human review? If that’s unanswered, we haven’t finished a migration; we’ve created two writable copies. Chapter 9’s rule: technical permission isn’t architectural authority. ⟲

Not every migration needs ongoing synchronization. If we’re replacing the legacy system completely, Day 0 comes, the final deltas load, reconciliation passes, users move, the old system goes read-only and is eventually archived or retired. Don’t build a permanent integration because “migrations usually have integrations.” If the old system is dead, stop feeding it. That’s RouteDesk: on Monday it’s read-only, then it’s retired, and nothing syncs with it. The synchronization Steve Trucking does need is a different arrow, Salesforce to Snowflake, designed in chapter 9 and covered in module 5. ⟲

Klik untuk memperbesar

The gap closes, authority moves, and the migration ends. The Snowflake feed goes on. ⟲

The opposite happens too. A transition that lasts months, users active in both systems, business units moving at different times: synchronization may have to start before the migration is finished. Now the migration is still moving the historical baseline while synchronization keeps live records consistent, and that’s a much harder architecture. You need to know which process owns which changes, or the load and the sync overwrite each other. So define the boundary visibly: before this point we’re building the target state; after it we’re maintaining consistency. It might be a timestamp, a cutover event, a business-unit transition, an object-by-object switch, a watermark. If nobody can tell me whether a record belongs to the migration process or the synchronization process, we have overlapping ownership, and that’s where records get missed or processed twice. ⟲

Kembali Normal, Lalu Hypercare

Restore normal operation deliberately: automation, scheduled jobs, integrations, event consumers, agents, user access, in an order that matters. For Steve Trucking: take the bypass away from the migration user, switch the Change Data Capture subscriber back on from the cutover point (so Snowflake gets Monday’s changes, not the weekend’s load), run module 3’s one backfill, then let the coordinators in. Remember module 3’s catch-up storm: when an integration comes back, what does it think happened while it was off? When users come back, is every critical service actually ready? The return to normal is part of the cutover. ⟲

Lalu kita live, tetapi belum selesai. Selama periode stabilisasi (sebut saja hypercare), awasi error migrasi, kegagalan integrasi, otomasi yang tak terduga, duplikat baru, hubungan yang hilang, masalah kinerja, masalah data yang dilaporkan pengguna, dan pergeseran rekonsiliasi. Risiko migrasi tidak lenyap saat pengguna login.

Then clean up: temporary migration users and permissions, bypass settings, staging data, temporary scripts, migration-only configuration, files holding sensitive source data, temporary integrations, runbook access. Don’t leave migration scaffolding attached to production because “we might need it someday.” Temporary architecture needs an exit plan too. Don’t forget the preparation data store. After RouteDesk, it holds eight years of Recipients’ names, addresses and phone numbers in its raw tables. Keep what the retention policy says to keep, as evidence, then delete the rest, on a date someone owns. ⟲

Dan simpan buktinya: ekstrak terakhir, versi transformasi, file muatan, hasil job, file error, laporan rekonsiliasi, persetujuan, runbook dengan waktu sebenarnya, keputusan go/no-go, dan pengecualiannya. Tiga minggu kemudian seseorang akan bertanya apakah sebuah rekaman sudah salah sebelum migrasi atau karena migrasi. Anda seharusnya bisa menjawab. Percaya, tetapi verifikasi tidak berakhir saat pemuatan selesai.

AI Bisa Membantu Mengawasi Cutover. Go/No-Go Bukan Miliknya.

AI berguna di bawah tekanan cutover: meringkas kegagalan, mengklasifikasikan error, membandingkan laporan, menemukan anomali, melacak runbook, memunculkan penyimpangan dari latihan. Tetapi go/no-go menggabungkan bukti teknis, dampak bisnis, waktu tersisa, posisi rollback, dan toleransi risiko. AI bisa memunculkan buktinya. Manusia yang bertanggung jawab yang membuat keputusannya.

Di luar ujian: apa yang diubah AI. AI bisa membuat pemantauan dan rekonsiliasi cutover lebih cepat, terutama dengan menemukan pola di set data error dan validasi yang besar. Pertahankan kepemilikan manusia yang eksplisit atas go/no-go, rollback, dan penerimaan risiko migrasi yang belum terselesaikan.

Yang Diputuskan Arsitek di Sini

• The rehearsal depth, the Day −7 / Day −1 / Day 0 load plan and the rollback point (what loads early, hidden by sharing) and the runbook that makes production cutover repeatable. ⟲
• Bagaimana pengguna dikunci di luar dan dibiarkan masuk kembali, dengan pintu belakang dan pengguna smoke test, dan bagaimana otomasi, integrasi, dan agen dikendalikan selama itu.
• Kriteria go/no-go, prosedur rollback, dan titik setelahnya rollback tidak lagi menjadi pemulihan yang aman, serta data dan aliran data yang tidak diketahui yang harus ditemukan lebih dulu.
• Bagaimana migrasi dibuktikan dengan jumlah, total, pemeriksaan acak, dan laporan agregat, terhadap nilai harapan yang ditetapkan sebelum pemuatan.
• Validasi bisnis, bukti, dan stabilisasi setelah go-live apa yang dibutuhkan sebelum migrasinya selesai.

Cutover Adalah Pembuktian

Skripnya berjalan: belum cukup. API mengembalikan sukses: belum cukup. Jumlah barisnya cocok: tetap belum cukup. Saya ingin jumlah, total, pemeriksaan acak, dan laporan agregat, validasi bisnis, sistem yang kembali normal, pengetahuan apakah kita masih di dalam jendela rollback, dan bukti tentang apa persisnya yang terjadi. Cutover produksi seharusnya membosankan, karena kita sudah melakukan pemikiran yang berat sebelum Jumat malam. Percaya, tetapi verifikasi. Lalu biarkan pengguna kembali masuk.

Jelajahi

• Others who cut over the same way: Salesforce Help, B2C Commerce Realm Split FAQ (terbuka di tab baru); Microsoft Learn, Data migration planning for go-live (terbuka di tab baru); AWS, Components of AWS DMS (terbuka di tab baru); all checked 2026-11-01. ⟲
• Salesforce Help: Freeze or Unfreeze User Accounts (terbuka di tab baru) and Custom Login Flows (terbuka di tab baru) (login flows are assigned by profile), checked 2026-11-01. ⟲
• Di kursus ini: Data Master dan Identitas dan Integrasi dan Perpindahan Data.