Changing a mobile number can break more of a home-security system than the alarm app. The old number may still receive sign-in codes, monitoring callbacks, delivery alerts, lock invitations, camera notices, billing messages, and account-recovery prompts. A successful number change is therefore not “the app opens on my phone.” It is proof that the old number has lost authority and the new number receives every message that matters.
Scope: this checklist covers a planned number change. If the old number was taken over without permission, use the SIM-swap response checklist first. If the phone itself is being replaced but the number stays the same, use the security-system phone replacement checklist. Do not factory-reset a working alarm, lock, camera, or hub merely because a contact record is wrong.
Start with a phone-number dependency map
List every place where the old number appears before the carrier releases it. Use current account pages, monitoring documents, saved invoices, password-manager records, household phones, and actual alerts. Do not assume one profile update will flow into every service.
| Dependency | What to record | Proof after the change |
|---|---|---|
| Alarm owner account | Sign-in, recovery, SMS, push, account owner, other administrators | New number saved; old number absent; owner can sign in through a tested recovery route |
| Professional monitoring | Primary callback, secondary contacts, passcode process, service address | Monitoring center reads back the new order and reaches each person in sequence |
| Smart locks and access | Owner account, phone keys, invitations, delivery or visitor credentials | Named users still work; old phone-number identity has no active credential |
| Cameras and video | Owner, viewers, SMS recovery, alert channels, export access | New number receives required notices; old number cannot recover the account |
| Garage and gate controls | Owner identity, shared access, alerts, service contacts | Normal and fallback entry work without granting the old number authority |
| Email and password manager | Recovery phone, MFA method, recovery codes, trusted devices | New recovery route tested without weakening MFA to SMS alone |
| Carrier account | Account PIN, port protection, authorized users, final date for old service | New line is controlled; old line is closed or released only after migration proof |
| Billing and permits | Invoices, financing, permit contacts, insurance certificate, service tickets | New contact appears on current records and future notices |
Keep this map with the broader home-security documentation record. Mark each dependency as changed, tested, or not applicable. A changed field is not yet a tested path.
Choose a controlled migration window
Make the change while the old number, new number, email, password manager, account owner, and a second household administrator are available. Avoid beginning immediately before travel, a move, a contractor visit, severe weather, a monitoring cancellation deadline, or a period when no one can safely test the property.
- Save current settings, contact order, user lists, device lists, alert rules, and monitoring records.
- Confirm that the account email is current and that its recovery path does not depend only on the old number.
- Store current recovery codes in an approved offline or password-manager record.
- Confirm one non-phone fallback for the home: mechanical key, keypad code, staffed contact, or another provider-approved route.
- Tell the household when the test starts, what alarms may occur, and who can stop the test safely.
- If professional monitoring is involved, ask how to place the account in a documented test mode without disabling local detection longer than needed.
Update identity accounts before accessory apps
Security products often inherit authority from an Apple or Google account. Update those records deliberately, then verify trusted devices and recovery choices. Apple publishes a process for adding and removing trusted phone numbers. Google publishes steps for changing a recovery phone number. Follow the current provider screens for the account and region; menu names and waiting periods can change.
Do not remove the old number until the new route is saved and a safe recovery path exists. After the change, review signed-in devices, recent security activity, app passwords, passkeys or security keys, recovery codes, and any household or family-sharing members. The goal is not to force every service onto SMS. Where a provider supports a stronger recoverable method, keep SMS as only the role the provider requires.
Change the alarm-system owner record
Open the alarm account from a known device and update the owner profile, alert contacts, SMS destinations, and recovery settings separately. If the platform distinguishes an account owner from household administrators, confirm which identity controls billing, monitoring changes, device removal, and user invitations.
Do not disarm, delete zones, remove the hub, or reset the panel as part of a contact change. Record the direct state of each protected opening before and after the migration. A functioning app is not proof that entry sensors, sirens, cellular communication, professional response, or local automations survived.
Alarm account acceptance checks
- Sign out and sign back in with the intended owner path.
- Confirm the new number on the owner profile and every alert/contact page.
- Confirm the old number does not remain as a recovery, SMS, or monitoring contact.
- Open and close one test door and verify direct zone state.
- Run one permitted arm/disarm test with a named user.
- Test internet loss or another documented failure path without removing the last working communication route.
- Record results in the monitoring and response test.
Call the monitoring provider and verify the contact tree
A profile screen may not update the monitoring center’s callback order, permit record, dealer system, or billing account. Use the provider’s published support route. Ask the representative to read back the primary number, secondary numbers, contact order, service address, verbal-passcode process, and any waiting period. Record the date, time, representative or ticket, and the exact fields confirmed.
Run a permitted test event. Verify who receives the first call or message, what happens when that person does not answer, and whether the second contact is reached. Never trigger an emergency dispatch merely to test a phone number. Follow the provider’s test-mode and local false-alarm rules.
Review smart-lock and physical-access authority
A phone number can appear in a lock-maker account, invitation, phone-key identity, delivery workflow, or household contact. Updating the alarm profile does not revoke those paths. Review the exact lock account and every connected smart-home platform.
- Keep one tested mechanical or maker-approved emergency path.
- Confirm the door latches freely before blaming an account change for motor trouble.
- Test the owner credential, one resident credential, one temporary credential, and inside egress.
- Remove only credentials tied to the old identity; do not erase valid household users in bulk.
- Audit codes with the named smart-lock access-code checklist.
- Check whether lock state and door-open state come from separate devices.
If a lock, gate, or garage controller relies on a vendor account plus Apple Home, Google Home, Alexa, Matter, or another controller, inspect both layers. Removing a number from one layer does not prove it disappeared from the other.
Check cameras, video access, and evidence ownership
Review owner and shared-viewer lists, recovery phone numbers, notification channels, cloud or local storage, export permissions, and camera privacy settings. Do not delete a camera or recorder to refresh a contact field. Preserve relevant footage before changing ownership or recovery settings.
Generate a harmless test event in one permitted view. Confirm that the new phone receives the expected alert, opens the correct clip or live view, and can export a sample if the household requires evidence access. Confirm that the old number is not offered as an account-recovery destination.
Test alerts as a response chain
An alert is useful only when the right person receives it, can identify the property and zone, can inspect evidence, and knows the next safe action. Test push, SMS, email, monitoring calls, and secondary contacts separately. Use the home-security alert delay test to record timestamps rather than relying on memory.
| Test | Expected result | Failure action |
|---|---|---|
| Entry sensor | Correct opening and state appear on the new phone | Check zone naming, app session, permissions, and hub path |
| Camera event | New phone opens the intended view or clip | Check notification permission, recording state, storage, and viewer role |
| Smart lock | Named user and state appear without exposing another resident | Check lock account, controller sharing, and code ownership |
| Monitoring callback | Provider follows the documented contact order | Reopen the monitoring ticket; do not assume app profile data is enough |
| Old number | No recovery code, security alert, or callback is sent there | Find the remaining record before releasing the number |
Do not release the old number too early
Keep the old line only as long as the carrier arrangement and household plan allow, but do not treat temporary access as a reason to delay the audit indefinitely. Set a migration deadline. Before the old number is closed or ported away, complete the dependency map, test every critical path, download needed records, and confirm the monitoring contact tree.
After release, assume another person may eventually receive that number. The security design should not depend on the future holder ignoring messages. Remove the old number from recovery, SMS, callbacks, invitations, billing, permits, and shared-access records rather than relying on carrier ownership.
60-minute home-security phone-number change acceptance test
- Minutes 0–10: compare the saved dependency map with current identity, alarm, monitoring, lock, camera, garage, billing, and carrier records.
- Minutes 10–20: sign out and back in through the intended owner account. Verify the new number, recovery method, trusted devices, and a second administrator.
- Minutes 20–30: test one direct entry zone, one permitted arm/disarm action, and the correct local siren or warning behavior.
- Minutes 30–40: test one smart-lock credential, inside egress, fallback entry, and one camera alert or evidence view.
- Minutes 40–50: run the provider-approved monitoring/contact-tree test and verify the secondary contact path.
- Minutes 50–60: search every account for the old number, close remaining gaps, and record the new baseline, tickets, timestamps, and rollback notes.
Pass rule: the new number and stronger recovery methods work, the old number has no remaining authority, direct security jobs still work, household and monitoring contacts follow the documented order, and at least one safe access route survives phone, internet, and account failures. If any critical path fails, keep the old line under control where possible, reopen the responsible account or provider ticket, and do not reset working devices as a shortcut.
Frequently asked questions
Is changing the number in the alarm app enough?
No. Monitoring callbacks, owner recovery, SMS alerts, billing, permits, smart-lock accounts, cameras, and identity providers may store separate records.
Should I remove the old number before adding the new one?
Add and test the new recovery/contact path first when the provider permits it. Then remove the old number and verify that it no longer receives codes, alerts, or calls.
Do I need to factory-reset the alarm or smart lock?
Normally, no. A planned contact change is an account and response-path task. Resetting hardware can erase zones, users, evidence, or the last working owner without fixing an external recovery record.
What if the monitoring center still calls the old number?
Reopen the provider ticket and ask for the monitoring contact tree to be read back. Record the representative, time, and test result. Do not assume the app profile and monitoring database are the same record.
Can I keep SMS as the only recovery method?
Use the strongest recoverable methods the provider supports. A phone number can be reassigned, ported, or temporarily unavailable, so the household should not depend on one SMS route for every security account.
When is the migration complete?
When the new number works, the old number has no authority, the monitoring tree is tested, direct alarm and access jobs still work, and the household has documented fallback entry and recovery routes.
Editorial boundary: this is an operating checklist, not carrier, legal, emergency-response, or account-recovery advice. Follow current instructions from the carrier, identity provider, security provider, monitoring center, insurer, and local authorities. Never create a real emergency dispatch for a test.
