# MapleJockey migration guides

Canadian tools. Clear evidence. Practical exits. | Source review: 2026-11-18

These five guides cover sales, marketing, security, research and defence. The route index records the checks completed for each guide. The Dropbox to Sync pilot restored a synthetic research dataset from a Canadian-region Sync account. The linked assessment workspace records evidence, gaps and acceptance results.

Scope targets, thresholds and effort ranges describe the proposed pilot designs. Observed results are dated in the relevant guide. They are not vendor guarantees or approved spending. Use existing authorised test environments, synthetic data and a named owner. A completed export is not a successful recovery exercise.

[Validation results](https://mj.foulkwerks.com/validation/index.html) · [Résultats de validation](https://mj.foulkwerks.com/validation/fr/index.html)

## Route index

| Sector | Source | Candidate destination | Verified coverage |
|---|---|---|---|
| Sales | HubSpot CRM | Maximizer CRM | Blocked · Maximizer access pending |
| Marketing | Mailchimp | Cyberimpact | Passed · 5 of 5 pilot checks |
| Security | LastPass | 1Password.ca | Partial · 1 passed, 4 blocked |
| Research | Dropbox | Sync.com, Canadian file-data region verified for this pilot | Passed · 5 of 5 pilot checks |
| Defence | Microsoft 365/SharePoint or another supplier evidence workspace | Secure workspace for a synthetic test; operational destination pending approval | Partial · 3 passed, 1 failed, 1 blocked |

## Move a HubSpot contact and company pilot to Maximizer

**Status:** Blocked · Maximizer access pending

HubSpot exported 20 contacts and five companies. All 20 associations reconciled. After a documented phone-format adjustment, all 160 mapped source values matched. Destination import, role checks and export await access to Maximizer.

A reversible CSV pilot for sales contact data. This is not a complete HubSpot replacement or a verified Canadian-residency configuration.

**Scope:** 20 synthetic contacts linked to 5 companies. Include names, primary email, phone, company and approved custom fields. Keep original record IDs in a migration ledger. Exclude deals, activities, email, attachments, automations, consent changes and live integrations.

### Before starting

- Use an already authorised isolated test account, or stop at local preparation. Confirm export and import permissions, destination licence entitlements, a named owner, and an empty import boundary. Do not buy licences for this exercise.
- Obtain the actual contracting entity and selected hosting region. Ask separately about production, backup, logs, telemetry, support access and subprocessors. A Canadian supplier address does not answer these questions.
- Agree a stable external-ID mapping, duplicate policy and company matching rule. Similar names and shared inboxes require manual review. Confirm whether destination custom fields can preserve source IDs.
- Record source SSO, MFA, roles and integrations. Specify what each sales user may see. Ask who can decrypt data and who can authorise key recovery; customer-managed keys do not by themselves establish exclusive customer control.

### Sequence

1. **Capture a baseline.** Record the source subset, object counts, required fields and contact-to-company relationships in a dated manifest. Save untouched exports separately from transformation copies. Disable all outbound actions in the isolated destination.

2. **Export the agreed objects.** Use HubSpot record export, with CSV, required properties and association IDs selected. The default view can omit fields and associations. Activity history has separate export routes. Use the current HubSpot guide rather than relying on remembered menu positions.

3. **Build and inspect the mapping.** Create one row per contact plus its chosen company. Map first name, last name, email, phone, company name and company website to Maximizer contact/company fields. Keep source IDs in approved custom fields or the external ledger. Mark secondary company associations as excluded unless explicitly rebuilt. Preserve accents, leading zeroes and telephone prefixes as text.

4. **Import one small batch.** Follow Maximizer’s current company/contact CSV import guide. Select the combined company-and-contact record type and explicitly set match fields. Prefer an empty test boundary; do not apply the example’s update-existing-records settings to a live database without a reviewed overwrite policy. Retain the mapping and import results.

5. **Reconcile and exercise the result.** Compare source rows, accepted rows, rejected rows and deliberate exclusions. Search every test contact, inspect its company link, edit one synthetic phone number and export/read it back. Check two user roles against the agreed access matrix.

6. **Close the pilot.** Record elapsed preparation, import and validation time separately. Document omissions and estimated remediation. Keep the original system authoritative. A production cutover requires a fresh delta plan, integration rebuild, access review and approved retention/deletion decision.

### Acceptance checks

- 20 of 20 intended contacts and 5 of 5 intended companies accounted for, with zero unexplained duplicate or missing records.
- 100% of required mapped fields and all intended contact-company links match the ledger; every rejected/excluded row has a reason.
- Accented names, apostrophes, multiline notes where in scope, phone prefixes and leading zeroes survive the pilot. No formula evaluation when inspecting CSV.
- Unauthorised test role cannot read restricted records; authorised role can search, edit and read back the synthetic change.
- Destination export/readback reconstructs the required pilot values. If export is unavailable in the selected plan, record a blocked exit gate, not successful recovery.

### What does not move automatically

| Object or capability | Treatment |
|---|---|
| Deals, pipelines, tasks, calls, email and attachments | Outside this route. Inventory and separately map or archive them before a production decision. |
| Multiple company associations and relationship labels | Explicitly map the supported relationship or retain an exceptions ledger; do not flatten silently. |
| Automations, forms, scoring, consent logic and integrations | Rebuild and test separately. Contact import does not recreate them. |
| Roles, audit history and SSO | Reconfigure and validate; CSV does not carry security policy. |

### Rollback

- Leave HubSpot records and integrations unchanged. Record destination batch IDs so only pilot-created records can be removed.
- Export any intentional pilot edits to the ledger before removing the test batch. For a live later cutover, reconcile new writes before switching authority back; never blindly overwrite source data.
- Retain protected original exports until the owner signs off the retention period. A failed pilot does not justify deleting the source account.

### Stop conditions

- A required field or relationship cannot be represented without accepted loss.
- Any unexplained duplication, disclosure, rejected row or update outside the pilot boundary.
- The destination tenant, legal entity or exit/export entitlement is unconfirmed.

**Effort:** Planning assumption: 0.5–1.5 operator days for this small pilot, excluding supplier responses, licence procurement and integration work. Not a quote or approved spend.

**Limits:** HubSpot exported 20 contacts and five companies. All 20 associations reconciled. After a documented phone-format adjustment, all 160 mapped source values matched. Destination import, role checks and export await access to Maximizer.

### Primary sources

- [HubSpot: Export your records](https://knowledge.hubspot.com/import-and-export/export-records) · checked 2026-11-18
- [HubSpot: Export contact data](https://knowledge.hubspot.com/import-and-export/export-contact-data) · checked 2026-11-18
- [Maximizer: Use the sample file to import companies and contacts](https://support.maximizer.com/hc/en-us/articles/23137320353037-Use-The-Sample-File-to-Import-Companies-and-Contacts) · checked 2026-11-18

## Move a Mailchimp contact pilot to Cyberimpact without losing suppression rules

**Status:** Passed · 5 of 5 pilot checks

The source export accounted for 15 contacts. Cyberimpact imported the eight consented test contacts, preserved the later opt-out on replay, and returned all 56 agreed field values through its contact and consent screens. No campaign was sent. A separate destination CSV download was blocked.

Prove contact and consent-field mapping before migrating campaigns. Protect suppressed contacts from accidental reactivation.

**Scope:** 20 synthetic contact records, including subscribed, unsubscribed, cleaned and consent-unknown examples. No live recipients, sends, domain changes or automations. Campaign design and reporting are separate work.

### Before starting

- Use the customer’s authorised registered users in its own isolated destination account, with sending disabled. Do not act as an intermediary sender for clients under the standard terms. Have the marketing owner approve the suppression ledger and the test consent evidence. Existing source subscription status is not, by itself, proof of a lawful basis to send.
- Confirm the supplier’s contracting entity, exact tenant arrangement and current data-processing terms. Obtain evidence for backups, logs, analytics, support access and deletion as well as contact storage.
- Identify custom fields, tags, groups, language preferences and consent evidence to preserve. Unknown dates remain unknown. Do not invent a consent date or mark an unknown contact as express consent.
- Confirm who can export audiences and who can import, send or change account settings. Document MFA/SSO requirements and recovery administrators.

### Sequence

1. **Export and separate contact states.** Use Mailchimp’s current audience export. Preserve the untouched ZIP and each state-specific CSV. Its contact export does not include campaign open/click reports, which require a separate report export. Record counts for every state, including suppressed records.

2. **Prepare two ledgers.** Create a source ledger with email, source ID, subscription state, group/tag, language and dated consent proof where it exists. Create a separate exclusion ledger for unsubscribed, cleaned, non-subscribed and unknown-consent examples. Do not merge these into a sendable import.

3. **Map a send-disabled test group.** Map email, names, custom fields and language to the destination. Preserve original consent timestamps in the source ledger; supply a date-only value only where the destination field requires it. Split by evidenced consent source rather than applying one default to mixed records.

4. **Import eligible synthetic records.** Use Cyberimpact’s current contact-list import, inspect field mapping and choose the appropriate consent source. Its mixed/unspecified choice can be treated as implied consent by the product; that is not acceptable evidence of permission for this pilot. Keep all unresolved records excluded.

5. **Prove suppression and report handling.** With sending and automations disabled, use the linked Cyberimpact instructions to mark a synthetic address unsubscribed. Confirm it appears under Unsubscribed and stays out of the draft recipient list after a repeat import. Record the result before considering any live migration.

6. **Evaluate remaining marketing work.** Rebuild one draft template and one segment using synthetic data if the existing authorised plan supports them. No email is sent. Record campaign reports, forms, automations, tracking, templates and deliverability configuration as separate migration tasks.

### Acceptance checks

- Every source record reconciles to eligible-imported, deliberately excluded or rejected. Zero unexplained records.
- Zero suppressed or consent-unknown examples appear in a sendable selection; if native suppression cannot be demonstrated, the live-send gate remains blocked.
- 100% of mapped names, language preferences and supported custom fields match; retained source consent evidence and timestamps remain accessible.
- Group membership and deduplication behave as documented for the pilot. Reimport does not silently broaden permission or create unintended recipients.
- A destination readback or export can reconstruct the agreed contact fields. No domain, DNS or live sending configuration changed.

### What does not move automatically

| Object or capability | Treatment |
|---|---|
| Contact status versus consent | Translate only evidenced permission. Retain source proof and suppression history; no automatic legal-compliance claim. |
| Campaign metrics and historic events | Export separately for archive/comparison; they do not become native Cyberimpact history through contact import. |
| Templates, journeys, forms, integrations and segmentation logic | Rebuild and test individually. Keep the first route contact-only. |
| Sending reputation and authenticated domains | Plan separately with the authorised domain owner. No DNS change is part of this demonstrator. |

### Rollback

- Keep Mailchimp authoritative and retain its suppression history. Remove only the synthetic destination batch after recording the results.
- For any later live cutover, capture new opt-outs on both systems and reconcile them before reverting. Never restore an earlier contact backup that reactivates an unsubscribe.
- Pause sending before rollback, retain the approved evidence ledger, and document deletion/retention at both providers.

### Stop conditions

- A suppressed or unknown-consent contact becomes sendable.
- Date conversion destroys original proof or unsupported defaults imply consent.
- The target suppression workflow or tenant data terms have not been verified.

**Effort:** Planning assumption: 0.5–1.5 operator days for contact mapping and suppression validation. Templates, deliverability, consent remediation and automation rebuild are additional. No price or licence spend approved.

**Limits:** The source export accounted for 15 contacts. Cyberimpact imported the eight consented test contacts, preserved the later opt-out on replay, and returned all 56 agreed field values through its contact and consent screens. No campaign was sent. A separate destination CSV download was blocked.

### Primary sources

- [Mailchimp: View or export your contacts](https://mailchimp.com/help/view-export-contacts/) · checked 2026-11-18
- [Cyberimpact: Import a contact list](https://faq.cyberimpact.com/en/articles/197/import-a-contact-list) · checked 2026-11-18
- [Cyberimpact: Prepare your contact list for import](https://faq.cyberimpact.com/en/articles/1363/prepare-your-contact-list-for-import) · checked 2026-11-18
- [Cyberimpact: Import contacts from Mailchimp (older route overview)](https://faq.cyberimpact.com/en/articles/230/how-to-import-your-contacts-from-mailchimp) · checked 2026-11-18
- [Cyberimpact: Terms and conditions](https://app.cyberimpact.com/terms-and-conditions?l=en_ca) · checked 2026-11-18
- [Innovation, Science and Economic Development Canada: Getting consent to send email](https://ised-isde.canada.ca/site/canada-anti-spam-legislation/en/getting-consent-send-email) · checked 2026-11-18
- [Cyberimpact: Manually unsubscribe contacts](https://faq.cyberimpact.com/en/articles/62/manually-unsubscribe-contacts) · checked 2026-11-18

## Pilot LastPass to a 1Password Canada account

**Status:** Partial · 1 passed, 4 blocked

Ten source records were observed across private and shared collections. The Canadian destination and sharing policy were verified. Destination reconciliation, role checks, recovery and final plaintext cleanup remain open.

Validate secret access and recovery as well as item counts. Canada-region secure-data storage is a scoped supplier claim, not proof that all service data stays in Canada.

**Scope:** 10 synthetic items, one private collection, one shared collection and two test roles in existing authorised test accounts. No production passwords, passkeys, recovery codes or client secrets.

### Before starting

- Confirm that the destination account is explicitly in the Canada region and document its business contract, DPA and subprocessors. Existing .com accounts do not change region merely by changing a billing address.
- 1Password’s region guide places Canada-account secure data in Canada. Its general privacy notice describes item-sharing and international service/support-data exceptions and says business customer data is governed separately. Obtain business-specific terms before treating the public notice as definitive for a tenant.
- Inventory shared-folder administrators, group membership, external users, SSO, MFA and recovery administrators. Verify the ability to create vaults and the importer prerequisites for the chosen authentication method.
- Identify the actual decryption and recovery model, including devices, Secret Keys, SSO and administrators. Do not infer exclusive customer key control from a key-management label. Keep a secure recovery path available throughout.

### Sequence

1. **Record the item and access baseline.** Use invented logins and attachments. Record item types, expected fields and access by user. Record unsupported types separately. Do not put secret values in the ordinary assessment evidence register.

2. **Use the supported importer.** Use the current 1Password desktop LastPass importer and explicitly select the Canada-region destination. Authenticate through the supported workflow. A direct importer avoids creating a routine plaintext CSV copy; if a file route is necessary, use an encrypted local working area and a documented deletion process.

3. **Review conversion differences.** Check the resulting tags, vaults and item types against the source. Review the importer’s unknown-data notes. The documented route does not import passkeys or LastPass Authenticator codes; private-item password history also differs. Re-enrol such credentials separately using service-owner-approved procedures.

4. **Validate shared access.** Check every synthetic shared item with both test roles, including a denied-access case. Shared-folder administration, membership and external users require special attention. Never assume that an imported permission set matches the original business intent.

5. **Demonstrate use and recovery.** On the approved test devices, retrieve an item, use a synthetic login and confirm the agreed account-recovery path. Export or copy the synthetic sample into an isolated readback boundary and verify it remains usable. Record whether files and non-login fields survive.

6. **Plan a staged cutover.** Record unsupported items, staff onboarding and browser-extension changes. Keep the source available until the owner signs off. Password rotation after a breach is a separate security action; moving the same secret does not repair exposure.

### Acceptance checks

- All 10 intended items and every expected non-secret attribute reconcile. Unsupported items have named owners and remediation, not silent omissions.
- Both allowed and denied shared-vault access behave as intended; no unexpected user receives access.
- Test retrieval works on the required devices and the recovery process succeeds for the synthetic account without relying solely on the source system.
- The destination’s Canada region and selected item-sharing settings are documented. Secure data, service data, diagnostics and support remain separately assessed.
- No plaintext credential file remains in a shared folder, browser download cache or ordinary evidence package after the controlled cleanup.

### What does not move automatically

| Object or capability | Treatment |
|---|---|
| Passkeys and LastPass Authenticator codes | The documented route excludes these. Plan explicit re-enrolment; retain the current working credential until verified. |
| Folders and item formats | Some structures become tags or vaults, and custom types may become notes. Inspect converted fields. |
| Private password history and external-user permissions | Do not assume parity. Record what is absent and rebuild access where approved. |
| Company identity and SSO policy | Reconfigure and test separately. A secret import does not migrate the organisation’s identity controls. |

### Rollback

- Keep the original synthetic account usable and protected. Remove only the trial vaults/items after preserving non-secret results.
- For a later live migration, reconcile any changed credentials before returning users to the source. Do not reintroduce superseded passwords.
- Restore normal MFA if any supported migration prerequisite changed it. Record and revoke temporary migration access. Do not delete the source account until recovery and unsupported-item gates pass.

### Stop conditions

- An authorised user cannot recover access or an unauthorised role can read a vault.
- Required passkeys or authenticator enrolments have no tested replacement.
- The destination region or business-specific data-processing terms are unconfirmed.

**Effort:** Planning assumption: 0.5–1 operator day for a synthetic two-role pilot; account setup, employee rollout, passkey re-enrolment and incident-driven rotation are additional. No paid account is assumed.

**Limits:** Ten source records were observed across private and shared collections. The Canadian destination and sharing policy were verified. Destination reconciliation, role checks, recovery and final plaintext cleanup remain open.

### Primary sources

- [1Password: Move data from LastPass in the desktop app](https://support.1password.com/import-lastpass/) · checked 2026-11-18
- [1Password: Regions](https://support.1password.com/regions/) · checked 2026-11-18
- [1Password: Notice of privacy practices](https://1password.com/legal/privacy) · checked 2026-11-18

## Move a research file subset from Dropbox to a verified Sync Canada region

**Status:** Passed · 5 of 5 pilot checks

All 30 synthetic files were restored with matching paths, sizes and hashes. The pilot verified access controls and functional readback. Original modification times changed. Individual downloads were verified; folder ZIP delivery remains unverified.

On 18 November 2026, the pilot used dedicated free Dropbox and Sync accounts. The signed-in Sync Billing page had no Data region section. Sync says this means the account uses its default Canadian file data region. An invited member used Chrome to download 30 files individually after their transfer from Dropbox. All paths, byte counts and SHA-256 hashes matched the originals across 23 subfolders (58,185 bytes). The 24 observations in the restored CSV files totalled 252. Access was denied before invitation and after removal. The member verified the edited journal and then the restored original.

**Scope:** 30 synthetic files under 100 MB, including CSV, PDF, plain text and an image, with nested folders and accented filenames. No human-participant data, confidential research, controlled goods, production credentials or AI training corpus.

### Before starting

- Confirm the exact selected Sync data region before copying anything. Its current privacy policy allows file data in Canada or the United States depending on region, and describes account-information processing in Canada and by US providers. Do not rely on older blanket Canada-only marketing.
- Confirm the contracting entity and business agreement. Current general terms distinguish Canadian and US entities by customer location; a separate business agreement can prevail. Determine backup, logs, support and deletion arrangements independently.
- Inspect the exact encryption settings and collaboration features, recovery administrators and who can obtain plaintext. Do not assume all optional features preserve the same encryption boundary.
- Check that both accounts and local devices are authorised, sufficient disk space exists, and selected source files are actually downloaded rather than online-only placeholders. Verify any research ethics, licence and third-party sharing constraints before a later live pilot.

### Sequence

1. **Create a file and permission manifest.** Record relative path, byte length, SHA-256 hash, file type and source timestamp for each synthetic file. Separately record intended user/role access. Keep a sealed original copy outside either synchronisation root.

2. **Download a bounded source copy.** Use the linked Dropbox folder-download instructions. Extract the downloaded archive into an isolated local staging directory. Reject archive entries that escape the staging root. Confirm all 30 files are ordinary usable files.

3. **Copy to the verified target.** Copy, rather than move, the staged files into a dedicated pilot folder using the supported Sync app or web interface. Keep Dropbox and Sync roots separate. Wait for transfer completion and inspect error/conflict notifications. Do not delete source files or the sealed original.

4. **Rebuild only required access.** Create the two approved synthetic test roles and a restricted share if existing entitlements support it. Check allowed and denied access. Do not recreate public links by default. Record whether downloaded copies remain outside later revocation control.

5. **Restore independently.** Download the target pilot folder to a clean local restore directory. Recompute every hash and byte length. Open each represented format and run a small CSV analysis from the restored files. Record restore start/end, bytes, count and failures.

6. **Record the exit decision.** Compare source, destination and restored manifests. Document any lost timestamps or metadata and test one approved edit followed by readback. A later production plan must address versions, deleted items, links, retention, identity and application dependencies separately.

### Acceptance checks

- 30 of 30 files restored; every file’s hash and byte length match the sealed original, with zero unexplained omissions or extra files.
- Folder hierarchy and accented filenames remain usable; all represented file types open, and the sample CSV analysis produces its expected result.
- Allowed test role can read the pilot; denied role cannot. Revoke the test share and confirm future access stops, while recording that already-downloaded copies cannot be recalled.
- Restore duration, transfer duration, target region, software versions and unresolved metadata/permission dependencies are captured.
- The original files remain unchanged and independently readable. Upload completion by itself is not a successful recovery test.

### What does not move automatically

| Object or capability | Treatment |
|---|---|
| Version history, deleted-item history and audit trails | Not preserved by ordinary file copying. Export/archive or rebuild separately. |
| Shared links, memberships and permissions | Recreate explicitly and test. Old links continue to reference the old service. |
| Cloud-native documents, comments and integrations | Identify separately; exported files may lose behaviour or metadata. No equivalence is assumed. |
| Research ethics, dataset licences and retention | Reassess applicability for the target arrangement. A Canadian location is not permission to transfer data. |

### Rollback

- Keep Dropbox authoritative and the sealed copy intact. Remove only the target pilot folder after recording results and any test edits.
- Pause the relevant synchronisation clients before cleanup if deletion propagation is uncertain. Never nest one provider’s sync directory inside the other.
- For a later live cutover, reconcile delta writes and sharing changes before rollback. Retain the agreed audit and research records even if the target is abandoned.

### Stop conditions

- Canada-region configuration cannot be evidenced or required support/key arrangements remain unacceptable.
- Any hash mismatch, incomplete placeholder download or excessive-access result.
- The dataset has unreviewed licence, ethics, contract or controlled-data restrictions.

**Effort:** Planning assumption: 0.5–1 operator day for the small file pilot, excluding supplier responses and large-data transfer time. Existing authorised storage only; no subscription purchase assumed.

**Limits:** All 30 synthetic files were restored with matching paths, sizes and hashes. The pilot verified access controls and functional readback. Original modification times changed. Individual downloads were verified; folder ZIP delivery remains unverified.

### Primary sources

- [Sync: Transfer files from Dropbox](https://help.sync.com/hc/en-us/articles/38275608488979-How-do-I-transfer-my-files-from-Dropbox-to-Sync) · checked 2026-11-18
- [Sync: Privacy policy](https://www.sync.com/privacy/) · checked 2026-11-18
- [Sync: Terms of service](https://www.sync.com/terms/) · checked 2026-11-18
- [Sync: General limits](https://help.sync.com/hc/en-us/articles/38275627279379-General-limits-when-using-Sync) · checked 2026-11-18
- [Dropbox: Download a file or folder](https://help.dropbox.com/sync/download-entire-folders) · checked 2026-11-18
- [Sync: Where to check your account’s data region](https://help.sync.com/hc/en-us/articles/38275625775379-Are-you-compliant-with-Canadian-data-privacy-legislation-PIPEDA-PIPA-FIPPA) · checked 2026-11-18
- [Sync: Download files or folders from the web panel](https://help.sync.com/hc/en-us/articles/38275630257555-How-to-use-the-Sync-com-web-panel) · checked 2026-11-18
- [Sync: Sharing limits on the Free plan](https://help.sync.com/hc/en-us/articles/55470306849811-What-are-the-limitations-of-the-Free-plan) · checked 2026-11-18

The [catalogue guide](MapleJockey_Canadian_Tools_and_Migration.html#guide/guide-dropbox-sync) links to the public validation results.

## Prepare a defence supplier document-workspace migration

**Status:** Partial · 3 passed, 1 failed, 1 blocked

The controlled test restored the ten synthetic documents and index. An uninvited account was denied access. The free plan granted edit access to an invited reviewer, which failed the required read-only role. Contract-specific requirements for real supplier data remain open.

Establish contract-specific requirements before choosing a migration destination. A Canadian product or hosting region is not a defence security approval.

**Scope:** One supplier evidence-exchange workflow and ten wholly synthetic files. Identify data categories, people, approvals and export limitations. No protected, classified, controlled-goods, export-controlled or confidential contract material is copied.

### Before starting

- Have the accountable security officer and contract owner classify the actual workload and identify applicable contract clauses. Protected/classified information, controlled goods and export controls are different questions; do not collapse them into a generic defence label.
- Where government contract IT requirements apply, obtain the required contract-specific authorisations and confirmation of the cloud assessment path. PSPC describes distinct supplier-system approval and cloud assessment requirements. A provider’s assessment is not approval of this customer deployment.
- For controlled-goods data, determine the organisation’s obligations and the provider/support-access scenario under current PSPC guidance. Confirm who may examine data, required personnel screening, records and incident handling before using any real material.
- Prepare a destination evidence request covering entity and ownership, all processing locations, backups, logs, support/subprocessors, identity, operational access, key use/recovery, export, deletion, incident response and exit assistance. Unknown answers remain blocking where the contract depends on them.

### Sequence

1. **Map the bounded workflow.** List document producers, reviewers and external recipients. Inventory files, permissions, versions, retention labels, legal holds, approval flows, links and integrations without copying document contents into the assessment. Reference actual clauses by ID and scope.

2. **Create the decision matrix.** For each candidate service, map mandatory customer requirements to dated evidence and exact product/configuration. Use pass/fail/undetermined per requirement. Do not calculate a blanket sovereignty score or treat sales material as government endorsement.

3. **Choose a candidate only after the evidence gate.** Obtain security-owner and contract-owner acceptance of the proposed configuration, including any required departmental or programme approvals. Document unresolved conditions and who can close them. No provider is selected by this guide.

4. **Design the export and mapping.** Obtain current source and destination documentation for the selected versions. Identify whether files, versions, metadata, retention, audit records and access rules can be exported/imported. If documented paths or entitlements are absent, stop before transfer rather than inventing commands.

5. **Run a synthetic rehearsal.** Once an approved test destination exists, use ten synthetic files with a checksum manifest and three roles: author, reviewer and denied user. Rebuild only the agreed workflow. Export back to a clean restore directory and demonstrate file integrity, permitted review and denied access.

6. **Prepare a separate live-change request.** Record measured rehearsal results, transfer path, delta capture, retention, rollback, key dependencies and support escalation. Real-data migration needs the applicable security and contractual approvals, an approved change window and a named rollback authority.

### Acceptance checks

- Every mandatory requirement has an evidence reference, date, scope and owner. Any unresolved requirement needed for real data keeps the live gate blocked.
- For an eventual synthetic rehearsal: 10 of 10 files restore with matching checksums; intended metadata and review states are accounted for; excluded history is explicit.
- Author/reviewer operations work and the denied role cannot view the files. Record audit visibility, account recovery and key-service dependencies.
- Restore time and completeness are measured. A downloaded archive alone does not establish operational recovery.
- The exact approvals, entities, deployment and data categories are recorded. No claim of general defence compliance or government endorsement appears in the result.

### What does not move automatically

| Object or capability | Treatment |
|---|---|
| SharePoint lists, workflows and application behaviour | Inventory separately; file export alone does not move the application. |
| Retention labels, holds, version history and audit | Require explicit preservation or accepted compensating records. A plain-folder copy is insufficient. |
| Security approval and screened support arrangements | Re-establish for the actual destination and contract. They do not transfer with files. |
| Customer-managed versus customer-controlled keys | Determine who can invoke decryption, recover keys and operate the service. A key-management option is not proof of exclusive customer control. |

### Rollback

- Keep the existing workspace authoritative during discovery and rehearsal. No production permissions, retention, DNS or identity changes occur.
- After a synthetic rehearsal, remove only the test boundary using the agreed procedure. Preserve non-sensitive test evidence.
- A later live rollback must reconcile edits, retain legal holds and records, restore approved access, and respect any required change notifications. Do not treat deletion of the destination as a universal rollback.

### Stop conditions

- The workload classification, contract scope or approval route is unresolved.
- The target provider/configuration lacks required evidence or authorised access arrangements.
- Any real controlled or sensitive data appears in the synthetic rehearsal.
- The source/destination export or restore route cannot be documented and tested.

**Effort:** Planning assumption: 1–2 operator days to assemble a bounded discovery record when documents are available. Supplier responses, specialist review and governmental approvals have no assumed duration or cost. No live-migration estimate is defensible yet.

**Limits:** The controlled test restored the ten synthetic documents and index. An uninvited account was denied access. The free plan granted edit access to an invited reviewer, which failed the required read-only role. Contract-specific requirements for real supplier data remain open.

### Primary sources

- [PSPC: Information technology security requirements](https://www.canada.ca/en/public-services-procurement/services/industrial-security/security-requirements-contracting/safeguarding-equipment-sites-assets-information/information-technology-security-requirements.html) · checked 2026-11-18
- [PSPC: Cloud solutions for controlled goods data](https://www.canada.ca/en/public-services-procurement/services/industrial-security/controlled-goods/program-requirements/guidance-using-providing-cloud-solutions.html) · checked 2026-11-18
- [Cyber Centre: Recommended cyber security contract clauses for cloud services](https://www.cyber.gc.ca/en/guidance/recommended-cyber-security-contract-clauses-cloud-services-itsm50104) · checked 2026-11-18
- [Cyber Centre: Guidance on cloud service cryptography](https://www.cyber.gc.ca/en/guidance/guidance-cloud-service-cryptography-itsp50106) · checked 2026-11-18
- [Government of Canada: Digital sovereignty framework](https://www.canada.ca/en/government/system/digital-government/digital-government-innovations/cloud-services/digital-sovereignty/digital-sovereignty-framework-improve-digital-readiness.html) · checked 2026-11-18

## Evidence to retain for every pilot

Keep the workload ID, guide/version, exact products and plans, approved data scope, operator, source and target configuration, timestamps, original exports, transformation rules, counts, checksums where appropriate, rejects/exclusions, functional results, access tests, elapsed time, rollback result, unresolved dependencies and decision owner. Do not put secret values or raw private records into a public directory or ordinary report.

Use Observed for actual recorded test results; Supplier-declared for provider statements; Document-reviewed for reviewed documentation; Inferred for reasoned conclusions; and Unknown where material is missing. Preserve Conflicting and Stale as separate states. This guide pack has no tenant-level Observed migration results.
